-
Bug
-
Resolution: Done
-
High
-
Dublin Release
With a very simple service while trying to use the GR-API and the default ONAP setting the following issues were found.
In the class org.onap.so.bpmn.infrastructure.workflow.tasks.WorkflowAction
the method selectExecutionList has the code
ServiceInstancesRequest sIRequest = mapper.readValue(bpmnRequest, ServiceInstancesRequest.class);
RequestDetails requestDetails = sIRequest.getRequestDetails();
String cloudOwner = "";
try
catch (Exception ex)
{ cloudOwner = environment.getProperty(defaultCloudOwner); } boolean suppressRollback = false;
try
catch (Exception ex)
{ suppressRollback = false; }the problem is that the cloudOwner isn't set in the Service request from vid and the Default cloud owner is not set in the override.yaml so query parameter don't get set correctly.
and then you get the error
"requestId": "df96c8f8-378e-420a-b3c7-9c4b85e59004",
"requestType": "createInstance",
"timestamp": "Fri, 10 May 2019 16:17:41",
"requestState": "FAILED",
"requestStatus": "STATUS: Exception in create execution list One or more of query value parameters are null.",
"percent-progress": "100"
05/10/19 16:17:40 HTTP Status: Accepted (202)
{
"requestReferences":
}
I think the value
org:
onap:
so:
cloud-owner: CloudOwner
should be set in the override yaml file
Also the defaults in the northbound_request_ref_lookup tables defined in ?(I can't find where this is defined) should be changed.
The CLOUD_OWNER should be CloudOwner not cloudOwner and SERVICE_TYPE should be * not NULL
- is duplicated by
-
SO-1904 Service Instantiation fails when using GR APIs
- Closed