OSC don't support compute service force down
Bug #1589348 reported by
Rui Chen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-openstackclient |
Fix Released
|
Undecided
|
Rui Chen | ||
Bug Description
Aims to evacuate servers from compute host as soon as possible, operators might set the compute host force down manually. Novaclient support the behavior, we should support it in OSC, like this:
openstackclient:
openstack compute service set [--up|--down] <host> <service>
novaclient:
nova service-force-down [--unset] <hostname> <binary>
| Changed in python-openstackclient: | |
| assignee: | nobody → Rui Chen (kiwik-chenrui) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-openstackclient (master) | #1 |
| Changed in python-openstackclient: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-openstackclient (master) | #2 |
| Changed in python-openstackclient: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/python-openstackclient 3.0.0 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/