-
Bug
-
Resolution: Done
-
High
-
El Alto Release
Trying to instantiate a macro service with one simple VNF, using GR-API (service types tried: vFW, vLB). The orchestration stops on CreateVnfInstance action.
It seems that orchestrator waits for "ack-final-indicator" = "Y" status from vnf-topology-operation, but it receives "ack-final-indicator" = "N". This is consistent to what SDNC provides:
_ackFinalIndicator=N for vnf-topology-operation
_finalIndicator=Y for vnf-topology-operation-async
2019-10-17T10:05:45,880 | INFO | qtp1468830967-120 | GenericResourceApiProvider | 258 - org.onap.sdnc.northbound.generic-resource-api-provider - 1.7.3 | - | Returned SUCCESS for vnf-topology-operation [8ab4f28a-ed66-4856-a6cc-8fe 74afd3835] VnfTopologyOperationOutput{_ackFinalIndicator=N, _responseCode=200, _responseMessage=, _serviceResponseInformation=ServiceResponseInformation{_instanceId=8ab4f28a-ed66-4856-a6cc-8fe74afd3835, augmentation=[]}, _svcRequestId=492c59f6-2f8f-4a8a-a9ec-bb0e74dcdafc, _vnfResponseInformation=VnfResponseInformation{_instanceId=c80587ce-c638-4a3d-a728-9152eae7a2b6, augmentation=[]}, augmentation=[]} (...) 2019-10-17T10:05:45,933 | INFO | Thread-90 | GenericResourceApiProvider | 258 - org.onap.sdnc.northbound.generic-resource-api-provider - 1.7.3 | - | Returned SUCCESS for vnf-topology-operation-async [8ab4f28a-ed66-4856-a6cc-8fe74afd3835] VnfTopologyOperationOutput{_ackFinalIndicator=Y, _responseCode=200, _responseMessage=, _serviceResponseInformation=ServiceResponseInformation{_instanceId=8ab4f28a-ed66-4856-a6cc-8fe74afd3835, augmentation=[]}, _svcRequestId=492c59f6-2f8f-4a8a-a9ec-bb0e74dcdafc, _vnfResponseInformation=VnfResponseInformation{_instanceId=c80587ce-c638-4a3d-a728-9152eae7a2b6, augmentation=[]}, augmentation=[]}
The so-bpmn-infra component only gets the response for vnf-topology-operation. It waits for one hour, nothing happens, and then rolls back changes.
In recent SDNC image (1.7.4) there was a change to use sync/async SO responses:
https://gerrit.onap.org/r/c/sdnc/oam/+/96756
I believe it may be the cause of this behavior.
Log files from so-bpmn-infra and from SDNC (/var/log/onap/sdnc/karaf.log) are attached.