Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1824331

Summary:	Baremetal IPI deployment with nodes running the baremetal network on a tagged vlan doesn't succeed because nodes try reaching MCS over the baremetal network which is not ready yet
Product:	OpenShift Container Platform	Reporter:	Marius Cornea <mcornea>
Component:	Installer	Assignee:	Kiran Thyagaraja <kiran>
Installer sub component:	OpenShift on Bare Metal IPI	QA Contact:	Raviv Bar-Tal <rbartal>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	high
Priority:	high	CC:	beth.white, ddharwar, dhellmann, sasha, shardy, wabouham, yprokule
Version:	4.4	Keywords:	Reopened, TestBlocker, Triaged
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-27 16:21:38 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:	1771572

Description Marius Cornea 2020-04-15 21:38:16 UTC

Description of problem:

Baremetal IPI deployment with nodes running the baremetal network on a tagged vlan doesn't succeed because nodes try reaching machine config server over the baremetal network which is not ready yet. 

Setup:
openshift nodes have 2 NICs grouped in a bond. Untagged traffic goes to provisioning network and baremetal network traffic goes over a tagged vlan configured on top of the bond. The network interfaces configuration is provided via ignition files.

When nodes first boot they try reaching the machine config server over the baremetal network but this fails because the vlan interface is not ready at this point. Instead the nodes should try reaching MCS over the provisioning network, at this point the NICs should have DHCP addresses on the provisioning network received from the bootstrap VM.

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-04-15-152338

How reproducible:
100%

Steps to Reproduce:
1. Deploy bare metal IPI with nodes having the baremetal network configured on a vlan interface.

Actual results:
Deployment is blocked because nodes cannot reach the machine config server.

Expected results:
Nodes reach the machine config server over the provisioning network instead of the baremetal network.

Additional info: