Attempting to Manage an Already Managed Share Will Succeed

[Yogesh]

This is a similar behavior to the one reported under cinder - https://bugs.launchpad.net/cinder/+bug/1364550

When issuing a manage command to a share that is already managed by Manila, the operation does not fail and you will wind up in an unexpected state. The operation will succeed, the backend storage will be renamed, and there will be two manila shares in the available state with only one of them being valid.

Steps to Reproduce -
1. Create manila share with NFS protocol (protocol should not matter here though)
2. Verify its created successfully.
3. Issue manage command using the same share that was created in above steps.

Result - On backend, the share will be renamed to the new manila share. However, on manila side there will be two shares in available state with only one being truly attached to the backend storage.

[Valeriy Ponomaryov (vponomaryov)]

Then Manila project should have been added to mentioned bug, and this one is duplication of https://bugs.launchpad.net/cinder/+bug/1364550

[Valeriy Ponomaryov (vponomaryov)]

And it is not reproducible for me, see http://paste.openstack.org/show/412519/

What version of Manila did you use to reproduce it? What driver?

[Jason Grosso (jgrosso)]

Is this is still occurring please open a new defect...