Can not delete share-network, that was used by driver
Bug #1273758 reported by
Valeriy Ponomaryov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Jun Wei Wang |
Bug Description
For share-network we expect next behavior:
1) if it is INACTIVE - we can delete it
2) if it is ACTIVE and there are shares, based on it, we can not delete it
3) if it is ACTIVE and no shares based on it, we should can delete it, and chain will be next:
manila verifies that no shares with dependency on it, and calls deallocation method, that releases resources taken from neutron, removes Vservers (service vms, etc...) and sets up INACTIVE state for share-network, after that delete method for share network.
Third item doesn't work.
tags: | added: share-network |
Changed in manila: | |
importance: | Undecided → Low |
Changed in manila: | |
assignee: | nobody → Jun Wei Wang (wjw7869) |
Changed in manila: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Covered by bp https:/ /blueprints. launchpad. net/manila/ +spec/share- network- activation- api
It is not implemented yet.