Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 874750 - man page for oo-accept-broker defines '-d' for two different options
man page for oo-accept-broker defines '-d' for two different options
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
1.2.0
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Luke Meyer
libra bugs
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-08 13:48 EST by Steve Reichard
Modified: 2017-03-08 12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-01-31 15:32:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0220 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 1.1 update 2013-01-31 20:23:24 EST

  None (edit)
Description Steve Reichard 2012-11-08 13:48:53 EST
Description of problem:

The man  page for oo-accept-broker indicated that option '-d' is for debug and '-d' is for dns.

(appears the DNS option can not be selected)

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.4-1.el6op                              @openshift_infrastructure
[root@Abroker2 ~]# 



How reproducible:

very

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Brenton Leanhardt 2012-11-09 08:41:57 EST
This will be fixed shortly after 1.0.
Comment 3 Luke Meyer 2012-12-13 14:22:43 EST
The second option should have been -D but as it wasn't doing anything anyway I just removed it.
Comment 4 xjia 2012-12-17 05:27:38 EST
It still has two "-d" options in man page,

Version:
OpenShiftEnterprise/1.1.x/2012-12-14.1/


Test:
SYNOPSIS
       oo-accept-broker [-hdv] [-a auth_service] [-s storage_service]
       [-d dns_service]
Comment 5 Luke Meyer 2012-12-18 20:47:17 EST
fixed with openshift-origin-broker-util-1.0.13-1.el6op
Comment 6 xjia 2012-12-19 03:40:11 EST
Verify:

oo-accept-broker(18 December 2012)          oo-accept-broker(18 December 2012)



NAME
       oo-accept-broker

SYNOPSIS
       oo-accept-broker [-h] [-v] [-d]


DESCRIPTION
       Verify  an  OpenShift  broker  is in a known valid state, or "accepted"
       good state. This is most often run with no options on the broker.

OPTIONS
       -h     Display a simple usage message and exit.

       -v     Enable verbose (INFO) output during the run of the script

       -d     Enable debugging mode (display every command executed)

EXAMPLE
       $ oo-accept-broker

HINTS
       This command should finish with output ’PASS’ and return code 0; other-
       wise the reasons for failure will be printed.

SEE ALSO
       oo-admin-ctl-district(8), oo-admin-move(8), oo-admin-chk(8), oo-accept-
       broker(8), oo-admin-ctl-app(8),  oo-admin-ctl-domain(8),  oo-admin-ctl-
       user(8), oo-register-dns(8)

AUTHOR
       Adam Miller <admiller@redhat.com> - man page written for OpenShift Ori-
       gin



                                            oo-accept-broker(18 December 2012)


[root@broker ~]# oo-accept-broker -h
usage: /usr/sbin/oo-accept-broker [-h] [-v] [-d]

  -h) Display this simple usage message and exit.
  -v) Enable verbose (INFO) output during the run of the script
  -d) Enable debugging mode (display every command executed)


Version:

OSE 1.1.x/2012-12-18.1
Comment 8 errata-xmlrpc 2013-01-31 15:32:19 EST
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

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