Capture and show VNF error reason in CLI and Horizon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
High
|
bharaththiruveedula |
Bug Description
Request for Enhancement:
When Tacker vnf-create API immediately fails (say due to bad image name or wrong flavor name) there is an error mesg (the reason for the failure is returned). However if the VNF fails,
a) after an attempt to start - say due to resource / host unavailable, some neutron/nova level errors
b) after a failure in healing action - say respawn limit is reached
.. the VNF state is simply moved ERROR state but no reason is display in CLI or Horizon. The operators, now, need to look at the logs to figure out what went wrong. This is huge usability issue.
Tacker's vnf-create backend logic need to be enhanced to ALWAYS capture a reason when a VNF is moved to error state, have this reason returned in vnf-show API and gets displayed both in tackerclient and tacker horizon UI.
Changed in tacker: | |
assignee: | nobody → bharaththiruveedula (bharath-ves) |
Changed in tacker: | |
assignee: | bharaththiruveedula (bharath-ves) → Sridhar Ramaswamy (srics-r) |
Changed in tacker: | |
assignee: | Sridhar Ramaswamy (srics-r) → bharaththiruveedula (bharath-ves) |
Fix proposed to branch: master /review. openstack. org/256314
Review: https:/