yahoo-eng-team team mailing list archive

[wei du <weidu@xxxxxxxxxxxxx>]

Public bug reported:

Currently, during nova-compute restart, when
CONF.resume_guests_state_on_host_boot is set true, all existing will be
put into ERROR state. In the patch, we just leave the instance in
POWEROFF 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’.

** Affects: nova
     Importance: Undecided
     Assignee: wei du (weidu)
         Status: In Progress

** Changed in: nova
     Assignee: (unassigned) => wei du (weidu)

** Changed in: nova
       Status: New => In Progress

-- 
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 POWEROFF state when nova compute restart with error

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  Currently, during nova-compute restart, when
  CONF.resume_guests_state_on_host_boot is set true, all existing will
  be put into ERROR state. In the patch, we just leave the instance in
  POWEROFF 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