Bug 2105345 - [Bare Metal IPI] BMH pre-provisoning netowrk configurations are not preserved when machineset replicas are scaled up/down
Summary: [Bare Metal IPI] BMH pre-provisoning netowrk configurations are not preserved...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.11
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Derek Higgins
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On: 2097695
Blocks: 2099584
TreeView+ depends on / blocked
 
Reported: 2022-07-08 15:49 UTC by Derek Higgins
Modified: 2022-07-08 15:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2099584
Environment:
Last Closed: 2022-07-08 15:50:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.