Instance reached to shutdown state and not able to re-spawn by tacker [In policy it’s defined to respawn in case of no accessibility]

Bug #1757962 reported by Manik Bindlish
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Won't Fix
Undecided
Unassigned

Bug Description

Release: Stable Newton
Ubuntu 16.04
Environment for NFV

Instance reached to permanent shutdown state and not able to re-spawn by tacker [In policy it’s defined to respawn in case of no accessibility]

1.) VNF created from tacker.

Below instance is created under tacker's VNF.

dharmendra@controller:~/toscatmplts$ nova list --all
+--------------------------------------+-------------------------------------------------------+----------------------------------+--------+------------+-------------+---------------------+
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------------------+----------------------------------+--------+------------+-------------+---------------------+
| 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed | ta-4034-9a0d-d35d24244dbe-RESPAWN-2-VDU1-updnuz4i3ncx | 3f63cd58b8394fe5a08b4d2bd2e97a71 | ACTIVE | - | Running | mgmt=192.168.104.21 |
+--------------------------------------+-------------------------------------------------------+----------------------------------+--------+------------+-------------+---------------------+

2.) Tried to migrate and stop nova instance at same time by keeping nova migration in background and nova stop command in foreground

dharmendra@controller:~/toscatmplts$ nova migrate 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed & nova stop 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed
[1] 23860

Request to stop server 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed has been accepted.
ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
<class 'nova.exception.UnexpectedTaskStateError'> (HTTP 500) (Request-ID: req-de9fd9aa-33f1-488e-9b90-f6d0bdace088)
dharmendra@controller:~/toscatmplts$
dharmendra@controller:~/toscatmplts$ nova list --all
+--------------------------------------+-------------------------------------------------------+----------------------------------+---------+------------+-------------+---------------------+
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------------------+----------------------------------+---------+------------+-------------+---------------------+
| 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed | ta-4034-9a0d-d35d24244dbe-RESPAWN-2-VDU1-updnuz4i3ncx | 3f63cd58b8394fe5a08b4d2bd2e97a71 | SHUTOFF | - | Shutdown | mgmt=192.168.104.21 |
+--------------------------------------+-------------------------------------------------------+----------------------------------+---------+------------+-------------+---------------------+
[1]+ Exit 1 nova migrate 9fc24e9a-5a14-48d6-8dd6-5868f85aa5ed

*Problem: Instance is reached permanent shutdown state and not able to respawn by tacker, whenever respawn policy was defined*

Revision history for this message
yong sheng gong (gongysh) wrote :

you need to look at if ping is still working

Revision history for this message
Manik Bindlish (manikbindlish19) wrote :

Ping was not working, status of instance was shutoff.

Yasufumi Ogawa (yasufum)
Changed in tacker:
status: New → Won't Fix
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.