yahoo-eng-team team mailing list archive

[Alex Syafeyev <astafeye@xxxxxxxxxx>]

Public bug reported:

I have a moltinode setup ( AIO ( machine 7)+ compute(machine 9))

I rebooted noncontroller host [9]

nova list --fields OS-EXT-SRV-ATTR:host,Networks,status

+--------------------------------------+-------------------------------+---------------------+--------+
| ID                                   | OS-EXT-SRV-ATTR: Host         | Networks            | Status |
+--------------------------------------+-------------------------------+---------------------+--------+
| 768ee44d-45d4-4e09-840b-b6492b7c0526 | 7   | int_net=192.168.1.8 | ACTIVE |
| c0297bcd-c480-4400-bbb8-66b463eb9d76 | 7 | int_net=192.168.1.9 | ACTIVE |
| 285fd146-e90f-4f83-be82-d56701dfe17b | 9 | int_net=192.168.1.6 | ACTIVE |
| afc3ce06-1fda-4354-8524-880e853cecf4 | 9 | int_net=192.168.1.7 | ACTIVE |
+--------------------------------------+-------------------------------+---------------------+--------+

only when the host goes up and VMs 192.168.1.6-7 go up with it we can
see the VMs in Shutdown mode.

Controller should know immediately if a host with VMs goes down.


Reproduction: 
1. configure multinode setup with VMs on both hosts . 
2. Reboot the noncontroller node. 
3. execute 
 nova list --fields OS-EXT-SRV-ATTR:host,Networks,status


more files attached in comments

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: nova-manage

** Attachment added: "nova-manage.log"
   https://bugs.launchpad.net/bugs/1464222/+attachment/4413183/+files/nova-manage.log

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1464222

Title:
  nova show -VM status incorrect

Status in OpenStack Compute (Nova):
  New

Bug description:
  I have a moltinode setup ( AIO ( machine 7)+ compute(machine 9))

  I rebooted noncontroller host [9]

  nova list --fields OS-EXT-SRV-ATTR:host,Networks,status

  +--------------------------------------+-------------------------------+---------------------+--------+
  | ID                                   | OS-EXT-SRV-ATTR: Host         | Networks            | Status |
  +--------------------------------------+-------------------------------+---------------------+--------+
  | 768ee44d-45d4-4e09-840b-b6492b7c0526 | 7   | int_net=192.168.1.8 | ACTIVE |
  | c0297bcd-c480-4400-bbb8-66b463eb9d76 | 7 | int_net=192.168.1.9 | ACTIVE |
  | 285fd146-e90f-4f83-be82-d56701dfe17b | 9 | int_net=192.168.1.6 | ACTIVE |
  | afc3ce06-1fda-4354-8524-880e853cecf4 | 9 | int_net=192.168.1.7 | ACTIVE |
  +--------------------------------------+-------------------------------+---------------------+--------+

  only when the host goes up and VMs 192.168.1.6-7 go up with it we can
  see the VMs in Shutdown mode.

  Controller should know immediately if a host with VMs goes down.

  
  Reproduction: 
  1. configure multinode setup with VMs on both hosts . 
  2. Reboot the noncontroller node. 
  3. execute 
   nova list --fields OS-EXT-SRV-ATTR:host,Networks,status

  
  more files attached in comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1464222/+subscriptions