Description of problem: The backport in bug 1932452 added the ability of the baremetal-operator to report a "provisioned registration error" for failures to adopt in ironic. Previously we reported adoption errors as a "registration error", but we needed to be able to distinguish between the two kinds. However, in 4.7 the cluster-baremetal-operator contains a separate copy of the BareMetalHost CRD, and this is the one that is installed in the cluster. This was not updated to allow the new value, with the result that writes that contain this errorType always fail with the following error: failed to save host status after "externally provisioned": BareMetalHost.metal3.io "openshift-master-0-1" is invalid: status.errorType: Unsupported value: "provisioned registration error": supported values: "registration error", "inspection error", "provisioning error", "power management error" This was detected in testing of bug 1972430, where an adoption error was induced by removing the image that the hosts were provisioned with.
So for the backport, I think the easiest is to just update the CRD in cbo.
OpenShift engineering has decided to NOT ship 4.8.6 on 8/23 due to the following issue. https://bugzilla.redhat.com/show_bug.cgi?id=1995785 All the fixes part will be now included in 4.8.7 on 8/30.
OpenShift engineering has decided to NOT ship 4.7.25 on 8/24 due to the following issue. https://bugzilla.redhat.com/show_bug.cgi?id=1995785 All the fixes part will be now included in 4.7.26 on 8/31.
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 (Important: OpenShift Container Platform 4.7.28 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. https://access.redhat.com/errata/RHSA-2021:3262