Boot time volume attachment lacks reservation of the volume till the completion of the attachment
Bug #1175648 reported by
Loganathan Parthipan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
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-
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.
Revision history for this message
| Michael Still (mikal) wrote | #1 |
| Changed in nova: | |
| status: | New → Incomplete |
| Changed in nova: | |
| assignee: | nobody → Vincent Hou (houshengbo) |
Revision history for this message
| haruka tanizawa (h-tanizawa) wrote | #2 |
Revision history for this message
| Loganathan Parthipan (parthipan) wrote | #3 |
| Changed in nova: | |
| assignee: | Vincent Hou (houshengbo) → nobody |
| Changed in nova: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
What version of nova are you using?