Deletes with nargs should follow a consistent pattern

Bug #1537856 reported by Terry Howe on 2016-01-25
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
python-openstackclient
Fix Released
Medium
Reedip

Bug Description

Deletes of resources with nargs should follow a consistent pattern where

* delete failures do not stop the delete of other resources
* a useful message gets printed for each failure
* $? should be non zero for partial failure

Similar to https://review.openstack.org/#/c/199665/

This should also include an updated to the developer docs which
documents the pattern for commands to follow.

Terry Howe (thowe-g) on 2016-01-25
description: updated
Richard Theis (rtheis) on 2016-01-28
description: updated
Reedip (reedip-banerjee) on 2016-02-10
Changed in python-openstackclient:
assignee: nobody → Reedip (reedip-banerjee)
Richard Theis (rtheis) wrote :

Another consideration is whether or not it should be considered a delete failure if the resource does not exist. The question was raised by Brad Behle here: https://review.openstack.org/#/c/278209/3

Fix proposed to branch: master
Review: https://review.openstack.org/296891

Changed in python-openstackclient:
status: New → In Progress

Change abandoned by Steve Martinelli (<email address hidden>) on branch: master
Review: https://review.openstack.org/296891
Reason: i believe this work is already finished

Steve Martinelli (stevemar) wrote :

Several of these have been implemented without referencing this bug. Let's take them on a case by case basis with new bugs.

Changed in python-openstackclient:
status: In Progress → Fix Released
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers