Bug 2091747

Summary: clusteroperator/baremetal stays in progressing: Applying metal3 resources state on a fresh install
Product: OpenShift Container Platform Reporter: Jacob Anders <janders>
Component: Bare Metal Hardware ProvisioningAssignee: Jacob Anders <janders>
Bare Metal Hardware Provisioning sub component: cluster-baremetal-operator QA Contact: Lubov <lshilin>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: high CC: augol, cgaynor, ealcaniz, imelofer, janders, kurathod, lshilin, openshift-bugs-escalate, openshift-bugzilla-robot, pibanezr, pmannidi, rpittau, sdasu, tsedovic, vkochuku, wking, zbitter
Version: 4.9Keywords: FastFix, OtherQA, Triaged
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2091738
: 2091748 (view as bug list) Environment:
Last Closed: 2022-06-09 06:41:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2091738    
Bug Blocks: 2091748    

Comment 5 Lubov 2022-06-03 14:05:01 UTC
as we discussed, since the problem is not reproduced on our setups, verifying this one as OtherQA after reviewing code changes.
Run the deployment with 4.9.0-0.nightly-2022-06-02-145128 to ensure nothing is broken

Comment 7 errata-xmlrpc 2022-06-09 06:41:54 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.37 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.