gluster_native: same volumes are re-used with vol mapped layout after restarting manila services
Bug #1501670 reported by
karthick
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
karthick |
Bug Description
Unlike directory based layout, with volume mapped layout a complete volume is picked to create a share. Volume thus picked should be used to create only one share.
However, shares created after manila service restart picks the volume once again although there is already a share created out of it. This is not expected.
Steps to reproduce:
1) create a backend gluster volume
2) create a share from the volume created above
3) Attempt to create share once again - share creation fails as there are no volumes to pick up - This is expected
4) restart all manila services - m-shr, m-api and m-sch
5) Attemp to create share once again - share gets created on volume which was already used in step 1
tags: | added: glusterfs |
tags: | added: liberty-rc-potential |
Changed in manila: | |
milestone: | none → mitaka-1 |
importance: | Undecided → High |
tags: |
added: liberty-backport-potential removed: liberty-rc-potential |
Changed in manila: | |
assignee: | Csaba Henk (chenk) → karthick (kramdoss) |
Changed in manila: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in manila: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/232293
Review: https:/