Bug 2038272 - Failures to build a PreprovisioningImage are not reported
Summary: Failures to build a PreprovisioningImage are not reported
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Zane Bitter
QA Contact: Eldar Weiss
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-07 16:40 UTC by Zane Bitter
Modified: 2022-03-10 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:37:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-baremetal-operator pull 231 0 None open Bug 2038272: Create image-customization-controller when metal3 Pod not up 2022-01-07 17:14:34 UTC
Github openshift image-customization-controller pull 28 0 None open Bug 2038272: Improve error reporting 2022-01-07 16:42:24 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:54 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.