Bug 1793115 - OVN expect nodeName is a hostname
Summary: OVN expect nodeName is a hostname
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.0
Assignee: Juan Luis de Sousa-Valadas
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On: 1798945
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-20 17:41 UTC by Vadim Rutkovsky
Modified: 2020-05-04 11:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: OVN expects node name to be the hostname Consequence: On clusters where this isn't true OVN will try to use node.metadata.name as the hostname, causing probles in name resolution. Fix: Get the node's hostname from the node.status.addresses Result: Node's hostname is always used to resolve the address regarding node.metadata.name
Clone Of:
Environment:
Last Closed: 2020-05-04 11:25:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ovn-org ovn-kubernetes pull 1017 0 None closed pkg/util: make GetNodeIP get the ip address from Kubernetes API 2020-04-17 09:14:52 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:26:15 UTC

Description Vadim Rutkovsky 2020-01-20 17:41:36 UTC 
Description of problem:

Current OVN setup requires node name to be the hostname, as `spec.nodeName` is passed to --init-node and later on used to find out the node name (https://github.com/ovn-org/ovn-kubernetes/blob/master/go-controller/pkg/util/kube.go#L102-L105).

This would break on CI's vSphere UPI, since it doesn't use FQDN names in /etc/hostname`.

Current workaround is to use IP in `/etc/hostname` to have nodeName == valid hostname.
Comment 3 Anurag saxena 2020-02-19 19:32:26 UTC 
Verification is pending due to awaited resolution on https://bugzilla.redhat.com/show_bug.cgi?id=1804482
Comment 6 errata-xmlrpc 2020-05-04 11:25:34 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.

https://access.redhat.com/errata/RHBA-2020:0581
Note You need to log in before you can comment on or make changes to this bug.