Bug 1368865 - diagnostic DClu3004 produces unnecessary Warning when masterURL is set as load balancer (not running Node host)
Summary: diagnostic DClu3004 produces unnecessary Warning when masterURL is set as loa...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.2.1
Hardware: All
OS: All
low
low
Target Milestone: ---
: ---
Assignee: Ravi Sankar
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 01:03 UTC by Kenjiro Nakayama
Modified: 2019-02-21 15:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-21 15:59:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2537641 0 None None None 2016-08-22 01:35:16 UTC

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
Note You need to log in before you can comment on or make changes to this bug.