Bug 1217587
Summary: | oo-admin-ctl-district command's district argument requirement is unnecessary | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | Node | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 2.2.0 | CC: | abhgupta, adellape, agrimm, anli, jhou, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan, sten, tiwillia, xiama |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-broker-util-1.34.1.1-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
Previously, all oo-admin-ctl-district commands required that the district name or UUID was specified. This made performing actions on multiple node hosts using oo-admin-ctl-district impossible if they were not in the same district. Additionally, finding the district a node host belonged to was difficult, requiring the administrator to sift through all district node hosts. This bug fix updates oo-admin-ctl-district to allow the district not to be specified for numerous actions; the district can still be specified manually with --uuid or --name options. As a result, the oo-admin-ctl-district command now searches for the correct district if no district is specified, and administrators can additionally perform actions on numerous node hosts across multiple districts.
|
Story Points: | --- |
Clone Of: | 1216191 | Environment: | |
Last Closed: | 2015-07-21 19:12:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1216191 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2015-04-30 18:08:51 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1463.html |