VNF lifecycle fails due to multiple causes

Bug #1902194 reported by Koichi Edagawa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
High
Koichi Edagawa

Bug Description

VNF lifecycle such as Scale, Rollback and Heal fails.
It is found that there are multiple causes of the failures, so I put those together into one report.

- It cannot set correct value to operation_params due to the lack of parameter setting in sending Notification
- 409 error occurs due to incorrect STATUS setting in Rollback
- Scale fails since instance_id/aspect_id cannot be set correctly
- HOT creation in Scale fails since API information cannot be set correctly
- In the case including recreating stack such as Heal, a waiting process fails due to un-updated instance_id
- Scale/Rollback fail since instance_id cannot be held during Instantiation
- Rollback fails due to incorrect state holding during Instantiation
- Uploading package in separate mode fails due to incorrect package extraction

description: updated
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/760523

Changed in tacker:
assignee: nobody → Koichi Edagawa (k-edagawa)
status: New → In Progress
Yasufumi Ogawa (yasufum)
Changed in tacker:
importance: Undecided → High
Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 5.0.0.0rc1

This issue was fixed in the openstack/tacker 5.0.0.0rc1 release candidate.

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.