Description of problem: oo-admin-ctl-district allows users to deactivate or remove nodes from a district, but requires the user to know the district in order to deactivate the node. Version-Release number of selected component (if applicable): openshift-origin-broker-util-1.23.8-1.el6oso.noarch How reproducible: Always Steps to Reproduce: 1. Attempt to deactivate or remove a node without specifying a district uuid or district name Actual results: $ sudo oo-admin-ctl-district -c deactivate-node -i ex-std-node424.prod.rhcloud.com --uuid or --name is required with command: deactivate-node Expected results: the activate-node, deactivate-node and remove-node commands should determine the proper district uuid to operate on the node. Additional info:
This is not really a bug but more like a simple enhancement to make it easier/simpler to activate/deactivate nodes.
*** This bug has been marked as a duplicate of bug 1216191 ***