No CLI support force delete for v3.23

Bug #1700927 reported by junboli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Triaged
Wishlist
Unassigned

Bug Description

Cinder support force delete volumes in version 3.23, in this case, Cinder API will ignore status check, but ensure snapshots are not part of a cgsnapshot. However, in cinderclient, no comand line support this feature. we expect the comand line is like this:

# cinder help delete
usage: cinder delete [--cascade <False|True>] [--force <False|True>]
                     <volume> [<volume> ...]

Removes one or more volumes.

Positional arguments:
  <volume> Name or ID of volume or volumes to delete.

Optional arguments:
  --cascade <False|True>
                        Remove any snapshots along with volume. Default=False.
  --force <False|True> Force to delete the volume. Default=False.

and the param force will be passed through cinderclient to cinder API, if the version is v3.23, then the param force will take effect.

junboli (junboli)
Changed in python-cinderclient:
assignee: nobody → junboli (junboli)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-cinderclient (master)

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

Changed in python-cinderclient:
status: New → In Progress
Eric Harney (eharney)
Changed in python-cinderclient:
importance: Undecided → Wishlist
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Bug Assignee Expired

Unassigning due to no activity for > 6 months.

Changed in python-cinderclient:
assignee: junboli (junboli) → nobody
status: In Progress → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.