openstack project delete should notify about it behaviour
Bug #2118900 reported by
Nikita Koltsov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-openstackclient |
New
|
Undecided
|
Unassigned | ||
Bug Description
It's not obvious for new users that openstack project delete is not checking if there are any resources assigned to this project. And it is inconsistent with other openstack commands like network delete is not working when there are ports/routers assigned to this network.
It would be better to remove such behavior, resources without a proper project are hard to find and fix after such removal. But it could be complex, so as a minimal safeguard it would be nice to notify user about such behavior and ask for additional confirmation as dialog option or as an additional flag
Revision history for this message
| Alexey Stupnikov (astupnikov) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to python-openstackclient (master) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix merged to python-openstackclient (master) | #3 |
To post a comment you must log in.
I don't like the idea of changing default behavior (so people's scripts will be broken with new release because we will ask for approval unconditionally). It is possible to calculate list of resources from project to be deleted and then take decision if project can be deleted, or extra approval is needed, but this is expensive.
I will add better command description as a first step and let others work on the rest (if they would want to).