NetApp cDOT driver is too strict in delete workflows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Clinton Knight |
Bug Description
If a share or share server is not created successfully, sometimes Manila will not save the vserver info in the share or share server object. In such cases, when asked to delete such a share or share server, the cDOT driver should not protest about the lack of vserver info but instead should log a warning and not raise an exception (which leaves the object in an error_deleting state).
Steps to reproduce -
1. Create a manila share.
2. Delete a vserver(on which this share resides) from backend.
3. Now try to delete this share.
Actual Result -
System throws below error -
2015-03-31 15:38:01.635 ERROR oslo_messaging.
Detailed logs -
http://
Changed in manila: | |
assignee: | NetApp (netapp) → Clinton Knight (clintonk) |
summary: |
- Manila cDOT driver is too strict in delete workflows + NetApp cDOT driver is too strict in delete workflows |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | kilo-rc1 → 2015.1.0 |
This is pretty serious bug because it prevents the development of negative tests. We need to be able to intentionally fail the creation of various things within Manila, and then to reliably clean up the garbage objects that get created.