yahoo-eng-team team mailing list archive

[Russell Bryant <1320628@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => juno-2

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

Title:
  Double powering-off state confuses the clients and causes gate failure

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  http://logs.openstack.org/52/73152/8/check/check-tempest-dsvm-
  full/9352c04/console.html.gz#_2014-05-13_18_12_38_547

  At client side the only way to know an instance action is doable is to
  making sure the status  is a permanent status like ACTIVE or SHUTOFF
  and no action in progress, so the task-state is None.

  In the above linked case tempest stopped the instance and the instance reached the  "SHUTOFF/None".
  'State transition "ACTIVE/powering-off" ==> "SHUTOFF/None" after 10 second wait'

  Cool, at this time we can start the instance right ? No, other
  attribute needs to be checked.

  The start attempt was rewarded with 409 :
   u'Instance 7bc9de3b-1960-476f-b964-2ab2da986ec7 in task_state powering-off. Cannot start while the instance is in this  state'

  The below line indicates the  task state, silently moved back to
  "SHUTOFF/powering-off"  , before the 'start' attempt.

  2014-05-13 18:09:13,610 State transition "SHUTOFF/powering-off" ==>
  "SHUTOFF/None" after 1 second wait

  Please do not set the 'None' task-state when the 'powering-off' is not
  finished.

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