Description of problem: oo-diagnostic error on broker No such file or directory - /etc/openshift/env/OPENSHIFT_BROKER_HOST As this file does not exist on broker Version-Release number of selected component (if applicable): 2.2.7 How reproducible: 100% Steps to Reproduce: 1. Upgrade from 2.2.7 to 2.2.8 2. run oo-diagnostics Actual results: FAIL: rescue in block in run_tests error running test_broker_certificate: #<Errno::ENOENT: No such file or directory - /etc/openshift/env/OPENSHIFT_BROKER_HOST Expected results: Error not to show up on broker since this file is on the nodes. Additional info: https://github.com/openshift/enterprise-server/blob/enterprise-2.2/common/bin/oo-diagnostics#L1378-L1448
Hi Ryan, That test_broker_certificate case is added to oo-diagnostics to run in the node only. It was not supposed to run on the broker. There is a code to check if it's a broker and it should skip that test. Unfortunately, the check code was incorrect and there is a PR to fix that on its way. Thanks, Vu
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/0ee0200df0c0167f99a07ba4e52e3af03fd180e5 Bug 1299095 - oo-diagnostic test_broker_certificate fails on broker The 'test_broker_certificate' method in oo-diagnostics fails if it's run on broker due to the fact the test will checking for a file that only exists on node but not broker. This is a regression issue as in PR 6275, several lines of code was added which was intended to run on the node only. As a result, when the code was run in the broker, the failure occurs. This commit will separate the code for broker and node test into 2 separate tests: test_broker_certificate and test_node_certificate. Bug 1299095 Link <https://bugzilla.redhat.com/show_bug.cgi?id=1299095> Signed-off-by: Vu Dinh <vdinh>
QE, Can we verify that oo-diagnostics will run successfully from both the broker and a node? Puddle: http://etherpad.corp.redhat.com/puddle-2-2-2016-02-19 Thank you
Verified and pass on puddle 2016-02-25.2
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/RHSA-2016-0489.html