DPDK: After rebooting a compute node DPDK VM's go into Error state
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
New
|
Medium
|
Michal Dubiel | |||
Trunk |
New
|
Medium
|
Michal Dubiel |
Bug Description
After rebooting a dpdk compute node VM';s on that node go into ERROR state , rather they should be in SHUTOFF state
If the VM are in ERROIR state then ADMIN need to first reset the state to active, shutdown the VM and then start the VM
If the VM is in SHUTOFF state , the admin just need to start the VM
root@cs-
+------
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+------
| f40b8ff2-
| fb424405-
| 251a4fae-
| ec81eaa1-
| b4eba1c7-
+------
Build 2717 Kilo
no longer affects: | juniperopenstack |
information type: | Proprietary → Private |
information type: | Private → Proprietary |
information type: | Proprietary → Public |
tags: | removed: releasenote |
I can not reproduce this, the VMs always change the status to shutoff after the node restart. Could you provide the testbed.py that was used for this? Perhaps it happens only in some particular configuration.