yahoo-eng-team team mailing list archive

[Jay Pipes <1330583@xxxxxxxxxxxxxxxxxx>]

As someone on one of the reviews commented, you can do a `nova reboot
--hard` to reboot a VM that is in ERROR state after a failed nova-
compute restart.

Closing this as Invalid.

** Changed in: nova
       Status: Confirmed => Invalid

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

Title:
  leave instances in original state when nova compute restart with error

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Currently, during nova-compute restart, when
  CONF.resume_guests_state_on_host_boot is set true and there is a
  problem during a nova-compute restart (for example, a network card has
  issues), all existing will be put into ERROR state.

  In the patch, we just leave the instance in original state. This way,
  we can directly run ‘nova reboot’ to get the instance back after
  errors got fixed.        With an instance in ‘ERROR’ state, one has to
  manually change the DB record to other state before running ‘nova
  reboot’.

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