VNF status should be ERROR instead of PENDING_UPDATE when update fails
Bug #1631752 reported by
jaff_cheng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
In Progress
|
Undecided
|
jaff_cheng | ||
Bug Description
Update VNF using a config-file with wrong syntax (such as a simple config file with content "foo:bar" which would be considered as a string) and VNF will stuck in PENDING_UPDATE status.
This VNF can't be updated or deleted properly any more.
Tacker should change the VNF status to ERROR in this case.
| Changed in tacker: | |
| assignee: | nobody → jaff_cheng (cheng-hang) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to tacker (master) | #1 |
| Changed in tacker: | |
| status: | New → In Progress |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/