Bug 1292222 - oo-admin-ctl-district new commands need to be added
Summary: oo-admin-ctl-district new commands need to be added
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Documentation
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-16 18:57 UTC by Vu Dinh
Modified: 2017-05-31 18:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-31 18:22:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vu Dinh 2015-12-16 18:57:31 UTC
Document URL: https://github.com/openshift/origin-server/blob/master/documentation/oo_administration_guide.adoc

Section Number and Name: 5.1.4. oo-admin-ctl-district

Describe the issue: 
In the doc, --command option is missing several options such as list and nodes-available:

-c|--command <command>
    (add-node|remove-node|deactivate-node|activate-node|add-capacity|remove-capacity|create|destroy)

Suggestions for improvement: 
The new or missing commands should be included:
(list|nodes-available|create|add-node|set-region|unset-region|deactivate-node|activate-node|remove-node|add-capacity|remove-capacity|destroy|publish-uids)

Additional information: 
Related to this PR: https://github.com/openshift/origin-server/pull/6337

Comment 1 Timothy Williams 2015-12-16 19:08:39 UTC
Note that the documentation also states that the list of districts can be obtained through running `oo-admin-ctl-distrct` with no arguments. This is now incorrect, and should be `oo-admin-ctl-district -c list`

Comment 2 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.


Note You need to log in before you can comment on or make changes to this bug.