Bug 1804944

Summary:	[IPI Baremetal] Hostname requirements are too restrictive
Product:	OpenShift Container Platform	Reporter:	Ben Nemec <bnemec>
Component:	Machine Config Operator	Assignee:	Ben Nemec <bnemec>
Status:	CLOSED ERRATA	QA Contact:	Victor Voronkov <vvoronko>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	4.4	CC:	amurdaca, aygarg, mnguyen, smilner, vvoronko
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Arbitrary hostnames for master nodes. Reason: Deployers will often have preferred naming formats for their hosts and will not want to use master-0, master-1, etc. Result: Master nodes can be named with any valid hostname.	Story Points:	---
Clone Of:
Clones:	1810663 (view as bug list)		Environment:
Last Closed:	2021-01-11 16:04:42 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:
Bug Blocks:	1810663

Description Ben Nemec 2020-02-19 22:42:51 UTC

Description of problem: Due to the need to map hostnames received from DHCP with the etcd-[0,1,2] DNS records, we have imposed restrictive requirements on the format of the hostnames for the master nodes. Many deployers will want to name their servers based on an internal scheme, so we need to eliminate these restrictions.

In 4.4 the cluster-etcd-operator was added, which should allow us to bootstrap the etcd cluster using the master hostnames directly and drop the etcd-specific records. However, some changes to the baremetal pod configurations are needed for that to work and we need to drop some hard-coded overrides in the coredns-mdns plugin.

Comment 10 Victor Voronkov 2020-04-20 18:37:10 UTC

Verified on 4.5.0-0.nightly-2020-04-14-031010

[core@master-0-0 ~]$ host -t SRV _etcd-server-ssl._tcp.ocp-edge-cluster.qe.lab.redhat.com
Host _etcd-server-ssl._tcp.ocp-edge-cluster.qe.lab.redhat.com not found: 3(NXDOMAIN)
[core@master-0-0 ~]$ host -t SRV _etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-2.ocp-edge-cluster-0.qe.lab.redhat.com.
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-1.ocp-edge-cluster-0.qe.lab.redhat.com.
_etcd-server-ssl._tcp.ocp-edge-cluster-0.qe.lab.redhat.com has SRV record 0 10 2380 master-0-0.ocp-edge-cluster-0.qe.lab.redhat.com.

Comment 12 errata-xmlrpc 2020-07-13 17:16:20 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:2409