Bug 1800746

Summary:	[IPI baremetal]: during bootstrap, two dhcp servers could be active on the provisioning network
Product:	OpenShift Container Platform	Reporter:	Stephen Benjamin <stbenjam>
Component:	Installer	Assignee:	Stephen Benjamin <stbenjam>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Nataf Sharabi <nsharabi>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	augol, rbartal, vvoronko
Version:	4.4	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Operators in the control plane can now start before bootstrap is fully complete. Consequence: Baremetal provisioning infrastructure could be active on both the bootstrap and control plane at the same time. Fix: Restrict bootstrap provisioning infrastructure to provision masters only. Result: Both provisioning infrastructures can be online at the same time.	Story Points:	---
Clone Of:
Clones:	1804793 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:14:25 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:	1804793

Description Stephen Benjamin 2020-02-07 20:15:33 UTC

The bootstrap VM can now co-exist with machine-api being up. That means there could be an instance of Ironic, dnsmasq, etc running in both the cluster and the bootstrap. This causes problems, as it's not deterministic which dnsmasq instance the worker provisioned by the machine-api will use. If bootstrap responds first then the worker will not come online as it'll be pointing at the wrong place.

This is causing a percentage of baremetal installs to fail, with the worker being offline, ingress and other operators never come up.

Comment 7 errata-xmlrpc 2020-07-13 17:14:25 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