"scaleLevel" is not changed after the LCM rollback operation

Bug #1946938 reported by Naoaki Horie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
In Progress
Medium
Naoaki Horie

Bug Description

I tried the scale out operation with a MgmtDriver in the tacker stable/wallaby releases, the scale out operation was failed.It's a created VNF Package issue by myself, so it's not a problem for the scale out operation to fail.However, a scaleLevel in the scaleStatus was "1" not "0".

---
$ openstack vnflcm scale --type SCALE_OUT --aspect-id free5gc_instance 0126ede2-84f4-4e18-996f-93cb68455945
Scale request for VNF Instance 0126ede2-84f4-4e18-996f-93cb68455945 has been accepted.
$
$ openstack vnflcm op list
+--------------------------------------+-----------------+--------------------------------------+-------------+
| ID | Operation State | VNF Instance ID | Operation |
+--------------------------------------+-----------------+--------------------------------------+-------------+
| 3dc2583e-479b-4b3f-ae8d-c5ebeea46c40 | FAILED_TEMP | 0126ede2-84f4-4e18-996f-93cb68455945 | SCALE |
+--------------------------------------+-----------------+--------------------------------------+-------------+
$
$ openstack vnflcm show 0126ede2-84f4-4e18-996f-93cb68455945 --fit-width
+--------------------------+-----------------------------------------------------------------------------------
| Field | Value
+--------------------------+-----------------------------------------------------------------------------------
| ID | 0126ede2-84f4-4e18-996f-93cb68455945
| Instantiated Vnf Info | {
| | "flavourId": "simple",
| | "vnfState": "STARTED",
| | "scaleStatus": [
| | {
| | "aspectId": "free5gc_instance",
| | "scaleLevel": 1 *
| | }
| | ],
---

And then, run the rollback operation, but the scaleLevel of scaleStatus remains at "1" and does not change to "0".

---
$ openstack vnflcm op rollback 3dc2583e-479b-4b3f-ae8d-c5ebeea46c40
Rollback request for LCM operation 3dc2583e-479b-4b3f-ae8d-c5ebeea46c40 has been accepted
$
$ openstack vnflcm op list
+--------------------------------------+-----------------+--------------------------------------+-------------+
| ID | Operation State | VNF Instance ID | Operation |
+--------------------------------------+-----------------+--------------------------------------+-------------+
| 3dc2583e-479b-4b3f-ae8d-c5ebeea46c40 | ROLLED_BACK | 0126ede2-84f4-4e18-996f-93cb68455945 | SCALE |
+--------------------------------------+-----------------+--------------------------------------+-------------+
$
$ openstack vnflcm show 0126ede2-84f4-4e18-996f-93cb68455945 --fit-width
+--------------------------+-----------------------------------------------------------------------------------
| Field | Value
+--------------------------+-----------------------------------------------------------------------------------
| ID | 0126ede2-84f4-4e18-996f-93cb68455945
| Instantiated Vnf Info | {
| | "flavourId": "simple",
| | "vnfState": "STARTED",
| | "scaleStatus": [
| | {
| | "aspectId": "free5gc_instance",
| | "scaleLevel": 1 *
| | }
| | ],
---

Therefore, retry the scale out operation with this status does not run.

---
$ openstack vnflcm scale --type SCALE_OUT --aspect-id free5gc_instance 0126ede2-84f4-4e18-996f-93cb68455945
can not scale_out
$
---

Changed in tacker:
assignee: nobody → Naoaki Horie (naoaki-horie)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tacker/+/814089

Changed in tacker:
status: New → In Progress
Yasufumi Ogawa (yasufum)
Changed in tacker:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.