image delete of non-existing image returns wrong message
Bug #2125401 reported by
Pavlo Shchelokovskyy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-openstackclient |
In Progress
|
Undecided
|
Pavlo Shchelokovskyy | ||
Bug Description
On current master and for some releases now, when trying to delete a non-existing image, the output is rather cryptic
❯ openstack image delete nonexisting
Multi Backend support not enabled.
besides, if any of the multiple images passed to command does not exists, the rest of the images won't be trying to delete.
Looks like since some time this `except not found` applies to both find_image and delete_image, instead of delete_image only as it was in the original patch that added `image delete --store` functionality.
https:/
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-openstackclient (master) | #1 |
| Changed in python-openstackclient: | |
| status: | New → In Progress |
| Changed in python-openstackclient: | |
| assignee: | nobody → Pavlo Shchelokovskyy (pshchelo) |
| description: | updated |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/