Add support for image deactivate and reactivate

Bug #1516661 reported by Niall Bunting on 2015-11-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Niall Bunting

Bug Description

Add support for image deactivate and reactivate. So admins can use the osc rather than the api.

Changed in python-openstackclient:
assignee: nobody → Niall Bunting (niall-bunting)
Changed in python-openstackclient:
importance: Undecided → Medium
status: New → Confirmed

Fix proposed to branch: master

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

Fix proposed to branch: master

Change abandoned by Niall Bunting (<email address hidden>) on branch: master
Reason: Abandoned in favour of:

Submitter: Jenkins
Branch: master

commit b3943d714275b276a973de9c52307e82c90be8bc
Author: NiallBunting <email address hidden>
Date: Mon Dec 14 14:28:45 2015 +0000

    Add image re/deactivate commands

    This change allows admins to deactivate and reactivate their
    images. Currently this has to be done with the REST api or the

    This change introduces `--deactivate` and `--activate` for the `image
    set` command.

    This requires glanceclient 1.2.0. Which got bumped here:

    Change-Id: I476c44a0343cdc92d58ddc93fb06470242de2345
    Depends-On: I2c370c6bf6ff664d94d756cc76aaa983fbdb8869
    Closes-Bug: 1516661

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

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

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

Other bug subscribers