Bug 2038272

Summary: Failures to build a PreprovisioningImage are not reported
Product: OpenShift Container Platform Reporter: Zane Bitter <zbitter>
Component: Bare Metal Hardware ProvisioningAssignee: Zane Bitter <zbitter>
Bare Metal Hardware Provisioning sub component: OS Image Provider QA Contact: Eldar Weiss <eweiss>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, eweiss, zbitter
Version: 4.10   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:37: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:

Description Zane Bitter 2022-01-07 16:40:46 UTC
Any errors that occur during reconciliation of a PreprovisioningImage resource are treated as transient and retried, reported only in the logs. This makes debugging difficult in cases where e.g. the user has provided invalid network data, the problem is not transient and must be addressed by a configuration change, thus it should be reported to the user.

In addition, in the case that we do not know the IP address of Ironic (because the metal3 Pod is not yet up), we still want to be able to reconcile the PreprovisioningImage resources and mark them as not ready. Currently we just crashloop, leaving the CRs in whatever their previous state was.

Comment 7 errata-xmlrpc 2022-03-10 16:37:38 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 (Moderate: OpenShift Container Platform 4.10.3 security 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.