yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. If you decide to work on this
consider using a blueprint [1] (maybe with a spec [2]). I'll recommend to 
read [3] if not yet done. 

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints

** Changed in: nova
       Status: Confirmed => 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/1397879

Title:
  User is not informed if reboot VM fail

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  The current workflow of rebooting a instance is:

  1. Reboot an active instance. If succeed, instance is still in active
  state.

  2. Reboot an active instance. If fail, and power_state is running,
  instance is still in active state.

  3. Reboot an active instance. If fail, and power_state is not running,
  instance will become error state.

  4. Reboot an error instance. If succeed, instance will become active
  state.

  5. Reboot an error instance. If fail, instance is still in error
  state.

  
  #1 and #2 are completely opposite result from user perspective. Especially, user should always hope to be informed, if his/her operation is not done as expected.  However, the instance information output by Nova api does not distinguish #1 and #2,  so that the user is not able to know if the reboot instance operation succeed or fail.

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