yahoo-eng-team team mailing list archive

[Raoul Hidalgo Charman <1753550@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

For instances that shut down themselves, the status remains Active, even
though the power state updates to Shutdown. If however the shutdown
signal is sent via openstack it does change the status to "SHUTOFF".

After creating an instance, the states are:
+------------------------+---------+
| Field                  | Value   |
+------------------------+---------+
| OS-EXT-STS:power_state | Running |
| OS-EXT-STS:task_state  | None    |
| OS-EXT-STS:vm_state    | active  |
| status                 | ACTIVE  |
+------------------------+---------+

Using openstack server stop results in:
+------------------------+----------+
| Field                  | Value    |
+------------------------+----------+
| OS-EXT-STS:power_state | Shutdown |
| OS-EXT-STS:task_state  | None     |
| OS-EXT-STS:vm_state    | stopped  |
| status                 | SHUTOFF  |
+------------------------+----------+

However logging into the instance and using the poweroff command results in:
+------------------------+----------+
| Field                  | Value    |
+------------------------+----------+
| OS-EXT-STS:power_state | Shutdown |
| OS-EXT-STS:task_state  | None     |
| OS-EXT-STS:vm_state    | active   |
| status                 | ACTIVE   |
+------------------------+----------+

This results in being unable to use the openstack server start command
on it fails and returns:

# openstack server start test_shutdown
Cannot 'start' instance 8881bebb-efbd-45e6-a052-7d23b9b63222 while it is in vm_state active (HTTP 409) (Request-ID: req-e473415d-d6e0-4342-b1f6-267efa934dc0)

despite the virtual machine being powered off. You can work around this
by running openstack server stop, and then openstack server start.

This is also an issue for external applications that check the status
(and how I noticed it to begin with).

This on devstack with commit id:
5d2add74534719c5670b29152964a60e8f23b42b

Not sure if the following is useful, but
- Using hypervisor libvirt+qemu/kvm:
# virsh version
Compiled against library: libvirt 3.2.0
Using library: libvirt 3.2.0
Using API: QEMU 3.2.0
Running hypervisor: QEMU 2.9.0
- Using ephemeral storage with ex4
- Neutron with OpenVSwitch

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1753550

Title:
  Status does not update to "Shutoff" when instance shuts down itself

Status in OpenStack Compute (nova):
  New

Bug description:
  For instances that shut down themselves, the status remains Active,
  even though the power state updates to Shutdown. If however the
  shutdown signal is sent via openstack it does change the status to
  "SHUTOFF".

  After creating an instance, the states are:
  +------------------------+---------+
  | Field                  | Value   |
  +------------------------+---------+
  | OS-EXT-STS:power_state | Running |
  | OS-EXT-STS:task_state  | None    |
  | OS-EXT-STS:vm_state    | active  |
  | status                 | ACTIVE  |
  +------------------------+---------+

  Using openstack server stop results in:
  +------------------------+----------+
  | Field                  | Value    |
  +------------------------+----------+
  | OS-EXT-STS:power_state | Shutdown |
  | OS-EXT-STS:task_state  | None     |
  | OS-EXT-STS:vm_state    | stopped  |
  | status                 | SHUTOFF  |
  +------------------------+----------+

  However logging into the instance and using the poweroff command results in:
  +------------------------+----------+
  | Field                  | Value    |
  +------------------------+----------+
  | OS-EXT-STS:power_state | Shutdown |
  | OS-EXT-STS:task_state  | None     |
  | OS-EXT-STS:vm_state    | active   |
  | status                 | ACTIVE   |
  +------------------------+----------+

  This results in being unable to use the openstack server start command
  on it fails and returns:

  # openstack server start test_shutdown
  Cannot 'start' instance 8881bebb-efbd-45e6-a052-7d23b9b63222 while it is in vm_state active (HTTP 409) (Request-ID: req-e473415d-d6e0-4342-b1f6-267efa934dc0)

  despite the virtual machine being powered off. You can work around
  this by running openstack server stop, and then openstack server
  start.

  This is also an issue for external applications that check the status
  (and how I noticed it to begin with).

  This on devstack with commit id:
  5d2add74534719c5670b29152964a60e8f23b42b

  Not sure if the following is useful, but
  - Using hypervisor libvirt+qemu/kvm:
  # virsh version
  Compiled against library: libvirt 3.2.0
  Using library: libvirt 3.2.0
  Using API: QEMU 3.2.0
  Running hypervisor: QEMU 2.9.0
  - Using ephemeral storage with ex4
  - Neutron with OpenVSwitch

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