yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

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

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

Title:
  Hard reboot escalation regression

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Nova used to allow a hard reboot when an instance is already being
  soft rebooted. However, with commit
  cc0be157d005c5588fe5db779fc30fefbf22b44d, this is no longer allowed.

  This is because two new task states were introduced, REBOOT_PENDING
  and REBOOT_STARTED (and corresponding values for hard reboots). A soft
  reboot now spends most of it's time in REBOOT_STARTED instead of
  REBOOTING.

  REBOOT_PENDING and REBOOT_STARTED were not added to the
  @check_instance_state decorator. As a result, an attempt to hard
  reboot an instance which is stuck trying to do a soft reboot will now
  fail with an InstanceInvalidState exception.

  This provides a poor user experience since a reboot is often attempted
  for instances that aren't responsive. A soft reboot is not guaranteed
  to work even if the system is responsive. The soft reboot prevents a
  hard reboot from being performed.

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