Description of problem: The description currently is: "Control user applicationsin OpenShift Origin." I believe there should be a space before the "in". Ideally a little mode explanation could be beneficial. Version-Release number of selected component (if applicable): [root@Abroker2 ~]# yum list installed openshift-origin-broker-util Loaded plugins: product-id, rhnplugin, security, subscription-manager Updating certificate-based repositories. Unable to read consumer identity Installed Packages openshift-origin-broker-util.noarch 1.0.2-1.el6op @openshift_infrastructure [root@Abroker2 ~]# How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fixed in https://github.com/openshift/origin-server/pull/834
This fix is not merged into 2012-11-06.7 yet. Will test it after patch is merged.
Retest this bug with openshift-origin-broker-util-1.0.5-1.el6op.noarch in 2012-11-12.1 puddle, looks like the pull did not merged yet. Could you help confirm that?
Please re-test this with the next 1.1.x puddle. Thanks!
Retest this bug with openshift-origin-broker-util-1.0.7-1.el6op.noarch in 1.1.x/2012-12-06.1 puddle, looks like the pull did not merged yet. So assign it back.
Wow, this was interesting. The fix mentioned in pull request was actually merged in. However the author fixed the man page directly. Currently we have txt2man documents as the source. When I fixed another man page bug I regenerated the oo-admin-ctl-app man page from the txt2man source... reverting the change that was man in the pull request. I double check and this fix will ship with the next 1.1.x puddle.
Verified this bug with openshift-origin-broker-util-1.0.8-1.el6op.noarch in 1.1.x/2012-12-09.1 puddle, and PASS. # man oo-admin-ctl-app <--snip--> NAME oo-admin-ctl-app SYNOPSIS oo-admin-ctl-app [-h|--help] [-l|--rhlogin rh_login] [-a|--app app_name] [-c|--command cmd] [-b|--bypass] DESCRIPTION oo-admin-ctl-app may be used to control and check the status of the OpenShift Origin hosted applications <--snip-->
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. http://rhn.redhat.com/errata/RHSA-2013-0220.html