SO is appropriately setting status to FAILED if the message to SDNC is failing on the “activate”
For Scenario II that you are running to becasue of the first failure , there is an issue that if the VF isnt in the “Active” state that the delete from SO to SDNC will fail. There is an updated DG for vnf-topology-operation-delete that relaxes that constraint. Pull a new copy of platform-logic<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=tree;f=platform-logic;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> / vnfapi<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=tree;f=platform-logic/vnfapi;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> / src<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=tree;f=platform-logic/vnfapi/src;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> / main<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=tree;f=platform-logic/vnfapi/src/main;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> / xml<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=tree;f=platform-logic/vnfapi/src/main/xml;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> / VNF-API_vnf-topology-delete.xml<https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=blob_plain;f=platform-logic/vnfapi/src/main/xml/VNF-API_vnf-topology-delete.xml;hb=b0e7aed1ffa2a4cdbcc60053532a1f265022146d> The root problem is why is the vnf-topology-operation-activate failing (at least that seems like the issue) Are there any errors in the SDNCAdapter log ? Brian From: onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> On Behalf Of Prakash via Lists.Onap.Org Sent: Monday, July 30, 2018 10:00 AM To: onap-discuss@lists.onap.org Cc: Kumar Skand Priya, Viswanath V <viswanath.kumarskandpr...@verizon.com> Subject: [onap-discuss] Error in SO when creating VF Module due to connectivity error with adopters - [SO] Hello, I have been trying to create vLB Demo using ONAP - R2, but the problem is SO is not stable/consistent when creating VF Module( Sometimes SO updates DB correctly, sometimes not). Scenario I: When creating VF Module . SO is not updating the DB with the Request status as " COMPLETE" even after instantiating the VFs in Openstack. Problem Statement: Installed ONAP Setup using OOM and when i tried creating VF Module SO's Database (DB: mso_requests Table:infra_active_requests) shows the Request status as "FAILED". But when i checked the openstack the vf module is actually successfully created and running. In the log i could see a connector error. Attathe Table Description and BPMN Error in the attachment. (BPMN Invoved in the Exception: SdnAdopter (Gets Timeout when waiting for asyn message)) LOG: errordev-so-85d5cf48c5-f27j8.log:10:2018-07-30T09:30:46.169Z|16de8444-9535-493e-9357-433326dd37cb|default task-416|MSO.CVFMI|BPMNClient|BPMN|MSO.CVFMI|ERROR|UnknownError|Caught ConnectorRequestException running Process[3c7dfa8b-93db-11e8-929c-02202d521919:3cb0a3ce-93db-11e8-929c-02202d521919] after receiving sdncAdapterCallbackRequest with SDNCA_requestId = '16de8444-9535-493e-9357-433326dd37cb-1532943045674': org.camunda.connect.ConnectorRequestException: HTCL-02007 Unable to execute HTTP request|MSO-BPEL-9101E Exception encountered ======================================================================================================================================== Scenario II: Creation of VF Module is success but the deletion has the above issue. Problem Statement: SO Creates the VF Module Successfully and updates the DB Request Status as " COMPLETE", but when i tried deleting the same it updates the DB as "FAILED" though it deletes the instance from openstack. In the log i could see a connector error. Added the Table Description in the attachment. (BPMN Invoved in the Exception: VnfAdopterRestV1(Gets Timeout when waiting for asyn message)) LOG: BPMN/errordev-so-85d5cf48c5-f27j8.log:17:2018-07-30T07:45:11.199Z|5d1bcea6-54f9-43b0-9d3c-fb65bfd9685d|default task-275|MSO.SDNCA|BPMNClient|BPMN|MSO.SDNCA|ERROR|UnknownError|Caught ConnectorRequestException running Process[72f54c9f-93cc-11e8-929c-02202d521919:72f83252-93cc-11e8-929c-02202d521919] after receiving WorkflowMessage with VNFAResponse_CORRELATOR = '5d1bcea6-54f9-43b0-9d3c-fb65bfd9685d-1532936694608': org.camunda.connect.ConnectorRequestException: HTCL-02007 Unable to execute HTTP request|MSO-BPEL-9101E Exception encountered BPMN/errordev-so-85d5cf48c5-f27j8.log:18:2018-07-30T07:45:11.200Z|5d1bcea6-54f9-43b0-9d3c-fb65bfd9685d|default task-275|MSO.SDNCA|BPMNClient|BPMN|MSO.SDNCA|ERROR|UnknownError|Caught ConnectorRequestException running Process[72f54c9f-93cc-11e8-929c-02202d521919:72f83252-93cc-11e8-929c-02202d521919] after receiving WorkflowMessage with VNFAResponse_CORRELATOR = '5d1bcea6-54f9-43b0-9d3c-fb65bfd9685d-1532936694608': org.camunda.connect.ConnectorRequestException: HTCL-02007 Unable to execute HTTP request|MSO-BPEL-9100E Exception: org.camunda.connect.ConnectorRequestException: HTCL-02007 Unable to execute HTTP request - at org.camunda.connect.httpclient.impl.HttpConnectorLogger.unableToExecuteRequest(HttpConnectorLogger.java:48) - at org.camunda.connect.httpclient.impl.AbstractHttpConnector.execute(AbstractHttpConnector.java:72) - at org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorImpl.execute(SoapHttpConnectorImpl.java:48) - at org.camunda.connect.httpclient.soap.impl.SoapHttpConnectorImpl.execute(SoapHttpConnectorImpl.java:23) - at org.camunda.connect.impl.AbstractConnectorRequest.execute(AbstractConnectorRequest.java:42) - at org.camunda.connect.plugin.impl.ServiceTaskConnectorActivityBehavior$1.call(ServiceTaskConnectorActivityBehavior.java:57) - at org.camunda.connect.plugin.impl.ServiceTaskConnectorActivityBehavior$1.call(ServiceTaskConnectorActivityBehavior.java:51) - at org.camunda.bpm.engine.impl.bpmn.behavior.AbstractBpmnActivityBehavior.executeWithErrorPropagation(AbstractBpmnActivityBehavior.java:108) - at org.camunda.connect.plugin.impl.ServiceTaskConnectorActivityBehavior.execute(ServiceTaskConnectorActivityBehavior.java:51) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationActivityExecute$2.callback(PvmAtomicOperationActivityExecute.java:57) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationActivityExecute$2.callback(PvmAtomicOperationActivityExecute.java:46) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl.continueIfExecutionDoesNotAffectNextOperation(PvmExecutionImpl.java:1958) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationActivityExecute.execute(PvmAtomicOperationActivityExecute.java:38) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationActivityExecute.execute(PvmAtomicOperationActivityExecute.java:27) - at org.camunda.bpm.engine.impl.interceptor.AtomicOperationInvocation.execute(AtomicOperationInvocation.java:91) - at org.camunda.bpm.engine.impl.interceptor.CommandInvocationContext.invokeNext(CommandInvocationContext.java:125) - at org.camunda.bpm.engine.impl.interceptor.CommandInvocationContext.performNext(CommandInvocationContext.java:104) - at org.camunda.bpm.engine.impl.interceptor.CommandInvocationContext.performOperation(CommandInvocationContext.java:79) - at org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.performOperation(ExecutionEntity.java:618) - at org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.performOperation(ExecutionEntity.java:594) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl$5.callback(PvmExecutionImpl.java:1897) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl$5.callback(PvmExecutionImpl.java:1894) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl.continueExecutionIfNotCanceled(PvmExecutionImpl.java:1964) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl.dispatchDelayedEventsAndPerformOperation(PvmExecutionImpl.java:1913) - at org.camunda.bpm.engine.impl.pvm.runtime.PvmExecutionImpl.dispatchDelayedEventsAndPerformOperation(PvmExecutionImpl.java:1894) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationTransitionNotifyListenerStart.eventNotificationsCompleted(PvmAtomicOperationTransitionNotifyListenerStart.java:57) - at org.camunda.bpm.engine.impl.pvm.runtime.operation.PvmAtomicOperationTransitionNotifyListenerStart.eventNotificationsCompleted(PvmAtomicOperationTransitionNotifyListenerStart.java:27) - at org.camunda.bpm.engine.impl.core.operation.AbstractEventAtomicOperation.execute(AbstractEventAtomicOperation.java:65) - at org.camunda.bpm.engine.impl.interceptor.AtomicOperationInvocation.execute(AtomicOperationInvocation.java:91) - at org.camunda.bpm.engine.impl.interceptor.CommandInvocationContext.invokeNext(CommandInvocationContext.java:125) NOTE: I have created JIRA ticke<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SO-2D774&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=mgsDUzjZL2FC2rLGkrLAQL-LmmggBWH4sJfyBtpXDf4&s=YViEMidBJ6ReDAkD1Q9m2qOmitFr5ZFKupHNOIHZJD8&e=>t on the same. Kindly Let me know is there anything can be done to avoid this inconistency in SO. Regards, Prakash Verizon -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11525): https://lists.onap.org/g/onap-discuss/message/11525 Mute This Topic: https://lists.onap.org/mt/23859940/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
