-
Bug
-
Resolution: Done
-
High
-
Guilin Release
-
SO-BPMN-INFRA 1.7.7, ONAP/OOM/Master as of 30.10.2020
Scenario:
Delete a VFModule instance, which hasn`t been orchestrated properly.
We expect the following BBs to be executed:
| 661 | VFModule-Delete | 3 | DeactivateVfModuleBB | 664 | VFModule-Delete | 4 | DeleteVfModuleBB | 667 | VFModule-Delete | 5 | UnassignVfModuleBB
What is currently executed, is this sequence:
| 661 | VFModule-Delete | 3 | DeactivateVfModuleBB | 664 | VFModule-Delete | 4 | DeleteVfModuleBB | 667 | VFModule-Delete | 5 | UnassignVfModuleBB | 919 | VFModule-Delete | 1 | ControllerExecutionBB | 1 | 133 | vnf | HealthCheck | | 922 | VFModule-Delete | 2 | ControllerExecutionBB | 1 | 133 | vfmodule | ScaleInReconfiguration | | 925 | VFModule-Delete | 6 | ControllerExecutionBB | 1 | 133 | vnf | HealthCheck |
The VFModule-Delete entries for ControllerExecutionBB have been probably included in the sequence by mistake (they look like ControllerExecutionBB entries for scale-out use-case).
I think, these ControllerExecutionBB entries need to be removed from the catalogdb.orchestration_flow_reference table.