yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #30892
[Bug 1175648] Re: Boot time volume attachment lacks reservation of the volume till the completion of the attachment
** Changed in: nova
Status: Incomplete => 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/1175648
Title:
Boot time volume attachment lacks reservation of the volume till the
completion of the attachment
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Volumes attached at boot can be accepted for attachment but before the
attachment completes it's possible for the volume to be used
elsewhere. The dynamic volume-attach reserves the volume by changing
the state from 'available' to 'attaching'. This needs to be done for
boot time attachments as well. But care should be taken to rollback
the state of the volume if the booting aborts.
Steps to recreate:
1. Boot an instance VM1 with block-device-mapping a volume V1.
2. Around the same time volume-attach V1 to another instance VM2.
It is likely that the volume V1 gets attached to VM2 and VM1 to ends
up in ERROR.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1175648/+subscriptions