OSC doesn't support deleting an in-use qos spec.

Bug #1596821 reported by aohuanxuan on 2016-06-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

Cinder V1 and V2 API support deleting an in-use qos spec with "--force" option. However, OSC doesn't support this argument.

aohuanxuan (huanxuan-ao) on 2016-06-28
Changed in python-openstackclient:
assignee: nobody → aohuanxuan (huanxuan-ao)

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

Changed in python-openstackclient:
status: New → In Progress
aohuanxuan (huanxuan-ao) on 2016-06-28
description: updated

Reviewed: https://review.openstack.org/334824
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=4e46c04f921c81927ded78f17fd28d5a55ebf9e2
Submitter: Jenkins
Branch: master

commit 4e46c04f921c81927ded78f17fd28d5a55ebf9e2
Author: Huanxuan Ao <email address hidden>
Date: Tue Jun 28 15:54:13 2016 +0800

    Add "--force" option to "volume qos delete" command

    Add ``--force`` option to ``volume qos delete`` command in volume
    v1 and v2 to allow users to delete in-use QoS specification(s).

    Change-Id: I46036e5f55ced8b8a1be54c521f2a5c242b89160
    Closes-Bug: #1596821

Changed in python-openstackclient:
status: In Progress → Fix Released

This issue was fixed in the openstack/python-openstackclient 3.0.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers