Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-454

ONAP Deployments Intermittently Fail when Instantiated through Portal


    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: High High
    • Amsterdam Release
    • Amsterdam Release
    • None

      When instantiating an ONAP deployment, the MSO's database occasionally doesn't update the action's status from "in progress" to "completed". Whether or not this occurs appears to be somewhat random.

      If you are creating your ONAP deployment manually, this is not an issue as everything will be up and running within OpenStack.

      However, your instantiation will fail if you are using Portal. Portal polls the MSO's database and will not complete the instantiation process until the action's status enters the "completed" state. As a result, Portal will occasionally hang when performing an ONAP deployment.

      This value is populated within the Request_Status field of the  INFRA_ACTIVE_REQUESTS table.

            gwarrack gwarrack
            gwarrack gwarrack
            0 Vote for this issue
            6 Start watching this issue