Bug 1976924 - "provisioned registration errors" cannot be reported
Summary: "provisioned registration errors" cannot be reported
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.7.z
Assignee: Angus Salkeld
QA Contact: Ori Michaeli
URL:
Whiteboard:
Depends On: 1977018
Blocks: 1972430
TreeView+ depends on / blocked
 
Reported: 2021-06-28 15:01 UTC by Zane Bitter
Modified: 2021-09-01 18:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The backport in bug 1932452 depended on a change in the Baremetal CRD. But the change was missed in the backport. Consequence: Saving the new value of host status always causes an error. Fix: The CRD changes are now backported. Result:
Clone Of:
Environment:
Last Closed: 2021-09-01 18:23:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-baremetal-operator pull 190 0 None None None 2021-08-09 23:58:25 UTC
Red Hat Product Errata RHSA-2021:3262 0 None None None 2021-09-01 18:24:19 UTC

Description Zane Bitter 2021-06-28 15:01:08 UTC
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.

Comment 3 Angus Salkeld 2021-08-09 23:36:55 UTC
So for the backport, I think the easiest is to just update the CRD in cbo.

Comment 7 ximhan 2021-08-20 08:00:10 UTC
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.

Comment 9 ximhan 2021-08-21 06:45:09 UTC
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.

Comment 12 errata-xmlrpc 2021-09-01 18:23: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 (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


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