Description of problem: 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. Version-Release number of selected component (if applicable): # rpm -qa | grep 'manila' python-manila-1.0.0.0-rc2.dev24.el7.centos.noarch python-manilaclient-1.4.1-dev3.el7.centos.noarch openstack-manila-1.0.0.0-rc2.dev24.el7.centos.noarch openstack-manila-share-1.0.0.0-rc2.dev24.el7.centos.noarch How reproducible: Always 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 5) Attempt to create share once again - share gets created on volume which was already used in step 1 Actual results: volume is re-used Expected results: volume should not be re-used Additional info:
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.