Bug 1913112 - BMC details should be optional for unmanaged hosts
Summary: BMC details should be optional for unmanaged hosts
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Angus Salkeld
QA Contact: Lubov
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-06 02:08 UTC by Angus Salkeld
Modified: 2021-07-27 22:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The code assumed that the Custom Resource (CR) would always have the Baseboard Management Controller (BMC) details, however in the assisted installer case the details are not provided. Fix: This change allows the CR to not have the BMC details when the operator is not creating the nodes (unmanaged).
Clone Of:
Last Closed: 2021-07-27 22:35:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift baremetal-operator pull 117 0 None closed Bug 1913112: Allow BMC details to be omitted for Hosts in Unmanaged state 2021-02-19 09:11:23 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:36:04 UTC

Description Angus Salkeld 2021-01-06 02:08:29 UTC
Description of problem:
When trying to enable baremetal on assisted installer the baremetal-operator is erroring with "no bmc details" (assisted installer does not provide bmc details).

Version-Release number of selected component (if applicable):

How reproducible:
Apply the following patches and create the cluster


Actual results:
baremetal-operator shows errors in the logs and does not set node linkage between entities.

Expected results:

Additional info:

Comment 3 Angus Salkeld 2021-01-17 23:10:25 UTC
Doc Text: This change allows CR to not have the BMC details in the case when the operator is not creating the nodes.

Comment 4 Lubov 2021-05-04 05:39:52 UTC
deployment works, BMH in good state

Comment 7 errata-xmlrpc 2021-07-27 22:35: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.8.2 bug fix and 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.