← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1310135] Re: Stopping an instance via the Nova API when using the Nova Ironic driver incorrectly reports powerstate

 

I agree with Sean - the real solution here is just to have a callback
mechanism between Ironic and Nova. Waiting for a periodic task to sync
the power state is not ideal, but it is "normal" for Nova today.

** Changed in: ironic
    Milestone: juno-rc1 => None

** Changed in: ironic
       Status: Confirmed => Won't Fix

** Changed in: ironic
       Status: Won't Fix => Opinion

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

Title:
  Stopping an instance via the Nova API when using the Nova Ironic
  driver incorrectly reports powerstate

Status in OpenStack Bare Metal Provisioning Service (Ironic):
  Opinion
Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  When using the Ironic Nova driver, a stopped server is still presented
  as Running even when the server is stopped. Checking via the Ironic
  API correctly shows the instance as powered down:

  stack@ironic:~/logs/screen$ nova list
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  | ID                                   | Name    | Status | Task State | Power State | Networks          |
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  | 5b43d631-91e1-4384-9b87-93283b3ae958 | testing | ACTIVE | -          | Running     | private=10.1.0.10 |
  +--------------------------------------+---------+--------+------------+-------------+-------------------+
  stack@ironic:~/logs/screen$ nova stop 5b43d631-91e1-4384-9b87-93283b3ae958
  stack@ironic:~/logs/screen$ nova list
  +--------------------------------------+---------+---------+------------+-------------+-------------------+
  | ID                                   | Name    | Status  | Task State | Power State | Networks          |
  +--------------------------------------+---------+---------+------------+-------------+-------------------+
  | 5b43d631-91e1-4384-9b87-93283b3ae958 | testing | SHUTOFF | -          | Running     | private=10.1.0.10 |
  +--------------------------------------+---------+---------+------------+-------------+-------------------+
  stack@ironic:~/logs/screen$ ping 10.1.0.10
  PING 10.1.0.10 (10.1.0.10) 56(84) bytes of data.
  From 172.24.4.2 icmp_seq=1 Destination Host Unreachable
  From 172.24.4.2 icmp_seq=5 Destination Host Unreachable
  From 172.24.4.2 icmp_seq=6 Destination Host Unreachable
  From 172.24.4.2 icmp_seq=7 Destination Host Unreachable
  From 172.24.4.2 icmp_seq=8 Destination Host Unreachable
  --- 10.1.0.10 ping statistics ---
  9 packets transmitted, 0 received, +5 errors, 100% packet loss, time 8000ms
  stack@ironic:~/logs/screen$ ironic node-list
  +--------------------------------------+--------------------------------------+-------------+--------------------+-------------+
  | UUID                                 | Instance UUID                        | Power State | Provisioning State | Maintenance |
  +--------------------------------------+--------------------------------------+-------------+--------------------+-------------+
  | 91e81c38-4dce-412b-8a1b-a914d28943e4 | 5b43d631-91e1-4384-9b87-93283b3ae958 | power off   | active             | False       |
  +--------------------------------------+--------------------------------------+-------------+--------------------+-------------+

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