yahoo-eng-team team mailing list archive

[lirenke <lvhancy@xxxxxxx>]

Public bug reported:

If I use block_device_mapping_v2 api to set a backend volume as boot device for instance. The instance will be launched by this remote volume successfully.
But, in such case, we can also use detach api to force this boot device being detached. So, when we do it, the guestOS of this instance would be damaged, and the whole system would not work normally if do a I/O operation. It seems can not resume.
I think we should give a warning for user at least or even forbiden this operation.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  detach boot device volume without warning

Status in OpenStack Compute (Nova):
  New

Bug description:
  If I use block_device_mapping_v2 api to set a backend volume as boot device for instance. The instance will be launched by this remote volume successfully.
  But, in such case, we can also use detach api to force this boot device being detached. So, when we do it, the guestOS of this instance would be damaged, and the whole system would not work normally if do a I/O operation. It seems can not resume.
  I think we should give a warning for user at least or even forbiden this operation.

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