Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1368865

Summary:	diagnostic DClu3004 produces unnecessary Warning when masterURL is set as load balancer (not running Node host)
Product:	OpenShift Container Platform	Reporter:	Kenjiro Nakayama <knakayam>
Component:	Networking	Assignee:	Ravi Sankar <rpenta>
Status:	CLOSED EOL	QA Contact:	Meng Bo <bmeng>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.2.1	CC:	aos-bugs, bandrade, bbennett, cdc, orhan.biyiklioglu
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-21 15:59:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kenjiro Nakayama 2016-08-22 01:03:57 UTC

Description of problem:

- diagnostic DClu3004 produces unnecessary Warning when masterURL is set as load balancer URL(not running Node host).

Version-Release number of selected component (if applicable):

- OpenShift Enterprise 3.2

How reproducible:

Steps to Reproduce:
1. Configure OpenShift Master with "masterURL: <LB's URL>" in /etc/origin/master/master-config.yaml
2. oc adm diagnostics --diaglevel=0

NOTE: Any Node doesn't run on LB host.

Actual results:

- Output Warn (Unable to find a node matching the cluster server IP.) as [1]

Expected results:

- Not output Warn as [2].

Additional info:

- A lot of users set "masterURL: <LB's URL>" in /etc/origin/master/master-config.yaml. Then, the LB doesn't have Node and got this Warning.

[1]
debug: Seaching for a node with master IP: [10.64.221.110]
debug: Checking node knakayam-ose32-master1.example.com address 10.64.221.196
debug: Checking node knakayam-ose32-master1.example.com address 10.64.221.196
debug: Checking node knakayam-ose32-master2.example.com address 10.64.221.177
debug: Checking node knakayam-ose32-master2.example.com address 10.64.221.177
debug: Checking node knakayam-ose32-master3.example.com address 10.64.221.71
debug: Checking node knakayam-ose32-master3.example.com address 10.64.221.71
debug: Checking node knakayam-ose32-node1.example.com address 10.64.221.245
debug: Checking node knakayam-ose32-node1.example.com address 10.64.221.245
debug: Checking node knakayam-ose32-node2.example.com address 10.64.221.216
debug: Checking node knakayam-ose32-node2.example.com address 10.64.221.216

WARN: [DClu3004 from diagnostic MasterNode@openshift/origin/pkg/diagnostics/cluster/master_node.go:175]
Unable to find a node matching the cluster server IP.
This may indicate the master is not also running a node, and is unable
to proxy to pods over the Open vSwitch SDN.

[2]
debug: Seaching for a node with master IP: [10.64.221.91]
debug: Checking node knakayam-ose32-smaster address 10.64.221.91
Info: Found a node with same IP as master: knakayam-ose32-smaster