Bug 2105345

Summary:	[Bare Metal IPI] BMH pre-provisoning netowrk configurations are not preserved when machineset replicas are scaled up/down
Product:	OpenShift Container Platform	Reporter:	Derek Higgins <derekh>
Component:	Bare Metal Hardware Provisioning	Assignee:	Derek Higgins <derekh>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Amit Ugol <augol>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	augol, dacarpen, derekh, fcristin
Version:	4.11	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.11.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2099584	Environment:
Last Closed:	2022-07-08 15:50:01 UTC	Type:	---
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:	2097695
Bug Blocks:	2099584

Description Derek Higgins 2022-07-08 15:49:28 UTC

+++ This bug was initially created as a clone of Bug #2099584 +++

This problem doesn't exist on 4.11, so the bug will be immediately closed

-

Description of problem:
network configurations added to BareMetalHost as day 1 with spec.preprovisioningNetworkDataName are not surviving machineset replicas scaling down and up again

Version-Release number of selected component (if applicable):
4.10

--- Additional comment from Derek Higgins on 2022-07-06 16:06:44 IST ---

Confirmed this happens on 4.10, it doesn't appear to be the case for 4.11, I'm trying to track down the difference.