Bug 1419472 - oadm diagnostics didn't report errors about MasterConfigCheck and NodeConfigCheck when DiagnosticName is not specified
Summary: oadm diagnostics didn't report errors about MasterConfigCheck and NodeConfigC...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Juan Vallejo
QA Contact: Xia Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-06 09:40 UTC by Xia Zhao
Modified: 2017-07-24 14:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-04-12 19:11:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0884 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.5 RPM Release Advisory 2017-04-12 22:50:07 UTC

Description Xia Zhao 2017-02-06 09:40:35 UTC
Description of problem:
When DiagnosticName = MasterConfigCheck|NodeConfigCheck:

Diagnose openshift system without DiagnosticName specified, errors are not reported:
# oadm diagnostics --master-config=/etc/nonfile
[Note] Running diagnostic: MasterConfigCheck
       Description: Check the master config file
[Note] Running diagnostic: NodeConfigCheck
       Description: Check the node config file

Diagnose openshift system with DiagnosticName specified, errors are reported:
# oadm diagnostics MasterConfigCheck --master-config=/etc/nonfile

[Note] Running diagnostic: MasterConfigCheck
       Description: Check the master config file
ERROR: [DH0002 from diagnostic MasterConfigCheck@openshift/origin/pkg/diagnostics/host/util.go:27]
       Could not read master config file '/etc/nonfile':
       (*os.PathError) open /etc/nonfile: no such file or directory

Version-Release number of selected component (if applicable):
openshift v3.5.0.16+a26133a
kubernetes v1.5.2+43a9be4
etcd 3.1.0

How reproducible:

Steps to Reproduce:
1.Refer to "Description of problem"

Actual results:
No error report when DiagnosticName is not specified for "MasterConfigCheck" and "NodeConfigCheck".

Expected results:
Should report error when DiagnosticName is specified for "MasterConfigCheck" and "NodeConfigCheck".

Additional info:
Issue did not repro for DiagnosticNames != MasterConfigCheck|NodeConfigCheck

Comment 1 Juan Vallejo 2017-02-06 19:32:25 UTC
Related PR: https://github.com/openshift/origin/pull/12832

Comment 2 openshift-github-bot 2017-02-09 10:13:25 UTC
Commit pushed to master at https://github.com/openshift/origin

bug 1419472
print master config error if it exists

Comment 3 Xia Zhao 2017-02-10 02:35:27 UTC
Tested with the latest puddle openshift v3.5.0.18+9a5d1aa, code is not merged into OCP. Will verify after it's in.

Comment 4 Troy Dawson 2017-02-10 22:50:27 UTC
This has been merged into ocp and is in OCP v3.5.0.19 or newer.

Comment 6 Xia Zhao 2017-02-13 06:38:37 UTC
Verified on the latest puddle, it's fixed.

# openshift version
openshift v3.5.0.19+199197c
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Comment 8 errata-xmlrpc 2017-04-12 19:11:40 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.


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