gluster_native: nfs vol mapped layout: shares created from snapshots aren't started, hence are inaccessible
Bug #1499347 reported by
karthick
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Csaba Henk |
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.
tags: | added: liberty-rc-potential |
tags: | added: driver glusterfs |
Changed in manila: | |
status: | New → In Progress |
assignee: | nobody → GlusterFS Drivers (glusterfs-drivers) |
Changed in manila: | |
importance: | Undecided → Medium |
Changed in manila: | |
milestone: | none → liberty-rc2 |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | liberty-rc2 → 1.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/228772
Review: https:/