"openstack share delete --force" command sends two separate API requests to delete share
Bug #2051737 reported by
Goutham Pacha Ravi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-manilaclient |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When using the "--force" option, the share delete command is expected to issue a POST /v2/shares/
The OSC command does this, but also issues a DELETE /v2/shares/
Changed in python-manilaclient: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /python- manilaclient/ +/907242 /opendev. org/openstack/ python- manilaclient/ commit/ 99be0ce9cc78b28 7170a5287c7bfd5 9038c7ecc2
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 99be0ce9cc78b28 7170a5287c7bfd5 9038c7ecc2
Author: Kiran Pawar <email address hidden>
Date: Tue Jan 30 17:27:41 2024 +0000
Fix share force delete case
Manilaclient force delete sends two REST requests, first
force delete and then delete. Fix it.
Change-Id: I8257c04f2b5f1a 02533dc0fa5d37a e6ff923a56a
Closes-Bug: #2051737