Multiattach - Multiattach is not being set correctly on volumes
Bug #1778525 reported by
Ciara Stacke
This bug report is a duplicate of:
Bug #1770671: multiattach is not enabled consistently when the default volume type supports multiattach.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
New
|
Undecided
|
Unassigned | ||
Bug Description
The multi-attach setting on a volume is only being set correctly for a standard 'create'. Creating a volume from source (volume or snapshot), managing an existing volume, or retyping to a multi-attach type, all fail to save the volume as multi-attach in the database.
To reproduce:
- Create a multi-attach volume type (extra-spec: multiattach='<is> True')
- Create a volume (volA) of the this type -> volume has multiattach flag set to True
- Create a clone of volA -> clone volume has multiattach flag set to False
The same result will be observed on create volume from snap, retype, and manage existing
Revision history for this message
| Eric Harney (eharney) wrote | #1 |
Revision history for this message
| Ciara Stacke (cstacke) wrote | #2 |
To post a comment you must log in.
This is likely related to the issues being addressed in bug 1770671.