Bug 1866348

Summary:	Wrong format for monitoring keepalived
Product:	OpenShift Container Platform	Reporter:	Yuval Goldberg <ygoldber>
Component:	Installer	Assignee:	Yuval Goldberg <ygoldber>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Amit Ugol <augol>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	urgent
Priority:	high	CC:	alazar, asegurap, beth.white, bperkins
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	OCP-Metal-External-Blocker
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-26 12:02:06 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:

Description Yuval Goldberg 2020-08-05 11:55:22 UTC

Description of problem:

Deploying multiple assisted installers where the user does not provide the VIP addresses with the same cluster name ends up with them competing for the same DHCP leased address and conflicting.

Version:
baremetal-runtimecfg 4.6

How reproducible:

Steps to Reproduce:
1. Deploy an assisted installer cluster without providing VIPs specifying clustername='reproducer'
2. Deploy another cluster on the same DHCP served network without providing VIP addresses and specifying the same clustername, i.e., 'reproducer'

Actual results:
Both the first and the second cluster ask DHCP for a lease with the same MAC address, thus the first cluster breaks as the address is taken by the second and the second fails to deploy.

Expected results:
Each cluster requests different addresses to DHCP so we keep allowing multiple clusters named the same

Comment 2 Ronnie Lazar 2020-08-26 12:02:06 UTC


*** This bug has been marked as a duplicate of bug 1866347 ***