Bug 1913112
Summary: | BMC details should be optional for unmanaged hosts | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Angus Salkeld <asalkeld> |
Component: | Bare Metal Hardware Provisioning | Assignee: | Angus Salkeld <asalkeld> |
Bare Metal Hardware Provisioning sub component: | baremetal-operator | QA Contact: | Lubov <lshilin> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | high | CC: | augol, hpokorny, kquinn, rbartal, stbenjam |
Version: | 4.7 | Keywords: | OtherQA, Triaged |
Target Milestone: | --- | ||
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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).
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 22:35: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: | |
Embargoed: |
Description
Angus Salkeld
2021-01-06 02:08:29 UTC
Doc Text: This change allows CR to not have the BMC details in the case when the operator is not creating the nodes. deployment works, BMH in good state 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. https://access.redhat.com/errata/RHSA-2021:2438 |