Share servers cannot be deleted with the generic driver
Bug #1877613 reported by
alpha23
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Queens: If a share server is deleted in nova, it remains in the share server list and cannot be deleted because it is in use by the generic shares which cannot be migrated or deleted which results in new shares on the same share network unable to be created because the share server for that share network does not exist.
Revision history for this message
| Goutham Pacha Ravi (gouthamr) wrote | #1 |
| Changed in manila: | |
| importance: | Undecided → Low |
| Changed in manila: | |
| status: | New → Triaged |
To post a comment you must log in.
We had a chance to discuss this at the community meeting. Please find logs here: http://
As a workaround, as an administrator, you can reset the state of the share server to error. This will prevent any further shares to be provisioned there. As for the existing shares, the driver currently doesn't provide a way to reconcile them if the share server is gone.
While we don't expect anyone to delete share servers provisioned by manila, it's a reasonable expectation for the driver to provide a way out of the mess that this would cause. I think we can create another share server and re-export the shares if the backend cinder volumes have not been deleted. However, this will need some heavy lifting in the driver.
Can I understand what is your use case for the generic driver? Are you just testing manila with it? or are you planning to use it in production? I ask because this driver isn't actively maintained to provide new features; it's used as a reference architecture driver for testing manila APIs. Over time we've had a lot of improvements to this driver, and we're very happy to accept these improvements from folks that intend to use this in production. If this is your use case, I'd be happy to work with you and get this bug addressed.