Description of problem: Nothing in Status: Settings section for masters $ oc describe hostfirmwaresettings openshift-master-2 -n openshift-machine-api Name: openshift-master-2 Namespace: openshift-machine-api Labels: <none> Annotations: <none> API Version: metal3.io/v1alpha1 Kind: HostFirmwareSettings Metadata: Creation Timestamp: 2021-11-30T15:31:51Z Generation: 1 Managed Fields: API Version: metal3.io/v1alpha1 Fields Type: FieldsV1 fieldsV1: f:metadata: f:ownerReferences: .: k:{"uid":"2cf106e5-41b6-42d1-a7cc-d8883cdf8ea5"}: f:spec: .: f:settings: Manager: baremetal-operator Operation: Update Time: 2021-11-30T15:31:51Z API Version: metal3.io/v1alpha1 Fields Type: FieldsV1 fieldsV1: f:status: .: f:conditions: .: k:{"type":"UpdateRequested"}: .: f:lastTransitionTime: f:message: f:observedGeneration: f:reason: f:status: f:type: k:{"type":"Valid"}: .: f:lastTransitionTime: f:message: f:observedGeneration: f:reason: f:status: f:type: f:schema: .: f:name: f:namespace: f:settings: Manager: baremetal-operator Operation: Update Subresource: status Time: 2021-11-30T15:32:20Z Owner References: API Version: metal3.io/v1alpha1 Block Owner Deletion: true Controller: true Kind: BareMetalHost Name: openshift-master-2 UID: 2cf106e5-41b6-42d1-a7cc-d8883cdf8ea5 Resource Version: 13974 UID: 8f1b64e0-a1ec-47a3-8c84-bf8442731bb2 Spec: Settings: Status: Conditions: Last Transition Time: 2021-11-30T15:32:20Z Message: Observed Generation: 1 Reason: Success Status: False Type: UpdateRequested Last Transition Time: 2021-11-30T15:32:20Z Message: Observed Generation: 1 Reason: Success Status: True Type: Valid Schema: Name: schema-4f53cda1 Namespace: openshift-machine-api Settings: Events: <none> Nothing in Spec: Schema for masters in corresponding schema object: $ oc describe firmwareschema schema-4f53cda1 -n openshift-machine-api Name: schema-4f53cda1 Namespace: openshift-machine-api Labels: <none> Annotations: <none> API Version: metal3.io/v1alpha1 Kind: FirmwareSchema Metadata: Creation Timestamp: 2021-11-30T15:32:20Z Generation: 1 Managed Fields: API Version: metal3.io/v1alpha1 Fields Type: FieldsV1 fieldsV1: f:metadata: f:ownerReferences: .: k:{"uid":"d266f73e-647d-4c87-a9da-b812779bbcf2"}: f:spec: .: f:hardwareModel: f:hardwareVendor: f:schema: Manager: baremetal-operator Operation: Update Time: 2021-11-30T15:32:20Z Owner References: API Version: metal3.io/v1alpha1 Kind: HostFirmwareSettings Name: openshift-master-1 UID: d266f73e-647d-4c87-a9da-b812779bbcf2 Resource Version: 13970 UID: c2c14b82-5046-4507-9466-93f1b4730ec8 Spec: Hardware Model: PowerEdge R740 (SKU=0715;ModelName=PowerEdge R740) Hardware Vendor: Dell Inc. Schema: Events: <none> Version-Release number of selected component (if applicable): 4.10.0-0.nightly-2021-11-29-191648 How reproducible: Steps to Reproduce: 1. Deploy a cluster 2. Run $ oc describe hostfirmwaresettings openshift-master-x -n openshift-machine-api 3. Run $ oc describe firmwareschema SCHEMANAME -n openshift-machine-api Actual results: see description Expected results: There should be settings in both. Otherwise don't see what we need the objects for masters Additional info:
Hi, could you paste all Metal3 logs? You're using a Redfish based driver, right? I'm not sure how/if the BIOS information is collected when adopting a master into the final cluster. CC'ing Bob for more insights.
I believe this is pending on the referenced PR as the Ironic API was being read before the settings were available, however, yes it would be useful to get the Metal3 logs along with the output of all the HSF resources ("oc get hsf -n openshift-machine-api -o yaml").
(In reply to Bob Fournier from comment #2) > I believe this is pending on the referenced PR as the Ironic API was being > read before the settings were available, however, yes it would be useful to > get the Metal3 logs along with the output of all the HSF resources ("oc get > hsf -n openshift-machine-api -o yaml"). Please, let me know if you need another logs
Thanks Lubov. Is it possible to get a must-gather so can see the BMO logs?
must-gather http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/BZ2027917-must-gather.tar.gz
It looks like this is resolved as of 4.10.0-0.nightly-2021-12-12-232810 with the fix https://github.com/metal3-io/baremetal-operator/pull/995/ merged downstream. All the masters and workers have settings and there is only one schema. [stack@localhost ~]$ oc get firmwareschema -n openshift-machine-api NAME AGE schema-c10e64ca 29m
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. https://access.redhat.com/errata/RHSA-2022:0056