Bug 1793115

Summary:	OVN expect nodeName is a hostname
Product:	OpenShift Container Platform	Reporter:	Vadim Rutkovsky <vrutkovs>
Component:	Networking	Assignee:	Juan Luis de Sousa-Valadas <jdesousa>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	cglombek, jdesousa, piqin, ricarril, scuppett
Version:	4.4
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:25:34 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:
Bug Depends On:	1798945
Bug Blocks:

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