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

Bug 2012684

Summary:	[IPI baremetal] The metal3 pod failed to restart when switching from Disabled to Managed provisioning without specifying provisioningInterface parameter
Product:	OpenShift Container Platform	Reporter:	Aleksandra Malykhin <amalykhi>
Component:	Bare Metal Hardware Provisioning	Assignee:	Angus Salkeld <asalkeld>
Bare Metal Hardware Provisioning sub component:	cluster-baremetal-operator	QA Contact:	Aleksandra Malykhin <amalykhi>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, asalkeld, athomas, hpokorny, sdasu, shardy, zbitter
Version:	4.9	Keywords:	Triaged
Target Milestone:	---	Flags:	sdasu: needinfo-
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2000081	Environment:
Last Closed:	2021-11-01 13:44:32 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:	2000081
Bug Blocks:

Comment 2 sdasu 2021-10-13 16:29:45 UTC

This is quite an important piece to complete https://issues.redhat.com/browse/MPINSTALL-6. So, thanks for taking a look @zaneb.

Comment 3 Angus Thomas 2021-10-13 16:37:52 UTC

We don't actually need to block 4.9 GA for this. We'll pudh to get the fix into a z-stream release as soon as possible.

Comment 6 Aleksandra Malykhin 2021-10-26 11:38:23 UTC

Verified on 
[kni@provisionhost-0-0 ~]$ oc get clusterversion
...
Cluster version is 4.9.0-0.nightly-2021-10-26-021742

Steps to reproduce:
1. Build the cluster with the Disabled provisioning and Redfish-VirtualMedia management type
2. Go through the masters and catch the boot mac addresses for available interfaces ( "enp0s3" in my case)
ssh core@master-0-0 & ip a
3. Edit the provisioning CR:
[kni@provisionhost-0-0 ~]$ oc edit provisioning-configuration

#Add the fields
provisioningDHCPRange: 172.22.0.10,172.22.0.100
provisioningIP: 172.22.0.3
provisioningNetworkCIDR: 172.22.0.0/24


#Change the privisioning network to Managed:
  provisioningNetwork: Managed

# Use the collected boot mac addresses to replace the followings:
  provisioningMacAddresses:
  - 52:54:00:7e:e8:79
  - 52:54:00:ee:e3:bc
  - 52:54:00:8e:a0:64
:wq

4. Verify the changes
[kni@provisionhost-0-0 ~]$ oc edit provisioning-configuration
Entered values are displayed in the CR 

[kni@provisionhost-0-0 ~]$ oc get pods -A | grep metal3
openshift-machine-api  metal3-6bd5dd6f4c-tdlkd      8/8    Terminating        1 (121
...
openshift-machine-api  metal3-86dccb65dd-ljwq6     10/10   Running            1 (21m 

The 8 pods were Terminated, 10 pods are running

Comment 9 errata-xmlrpc 2021-11-01 13:44:32 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 (OpenShift Container Platform 4.9.5 bug fix update), 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-2021:4005