gluster_native: nfs vol mapped layout: shares created from snapshots aren't started, hence are inaccessible
Bug #1499276 reported by
karthick
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| devstack-plugin-glusterfs |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
In glusterfs driver, with the introduction of volume mapped layout, we have the capability to create shares out of snapshots. Shares created from snapshots are inaccessible today and this needs to be fixed.
We create snapclones in the backend gluster cluster and the manila shares are then created on top of these snapclones. After creation of these snapclones it is required to 'start' them like we do for other gluster volumes. We don't start the volume in manila and thus the backend snap clones are in 'created' state instead of 'started' state. This makes the shares created from snapshots inaccessible. This has to be fixed.
Revision history for this message
| Ramana Raja (rraja) wrote | #1 |
| Changed in devstack-plugin-glusterfs: | |
| status: | New → Invalid |
To post a comment you must log in.
This bug is not related to this project. It should've been filed for the Manila project.