Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-45145

Firmware schemas not generated in two SNO spoke deployment

XMLWordPrintable

    • Important
    • None
    • 5
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause
      BMO is currently unable to access complete BareMetalHost data, including preconfigured HostFirmwareSettings.

      Consequence
      No firmware schemas are generated for SNO clusters and HostFirmwareSettings resources include requested settings, but not current settings detected during spoke deployment.

      Fix
      None available at the moment. The issue is being worked on.

      Result
      Only limited HostFirmwareSettings data is available on Single Node OpenShift (SNO)
      Show
      Cause BMO is currently unable to access complete BareMetalHost data, including preconfigured HostFirmwareSettings. Consequence No firmware schemas are generated for SNO clusters and HostFirmwareSettings resources include requested settings, but not current settings detected during spoke deployment. Fix None available at the moment. The issue is being worked on. Result Only limited HostFirmwareSettings data is available on Single Node OpenShift (SNO)
    • Known Issue
    • In Progress

      Description of problem:

      Deployment of two SNO spokes with Telco RAN DU profile via ZTP siteconfig that
includes using biosConfigRef to configure and validate BIOS settings of the
BMs, fails to generate firmwareschemas for the hosts so the BIOS profile is
not applied.

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

      OCP: 4.17.4 on hub
OCP: 4.18.0-0.nightly-2024-11-27-085927 on SNO spokes
ZTP site generate: v4.18.0-19
hub operators:
        advanced-cluster-management.v2.12.1
        multicluster-engine.v2.7.1
        openshift-gitops-operator.v1.14.2
        packageserver
        topology-aware-lifecycle-manager.v4.18.0

      How reproducible:

          Always

      Steps to Reproduce:

          1. create ZTP profile to deploy 2 SNO spoke clusters via ZTP with RAN DU profiles
    2. after deployment completes, check firmwareschema and hfs for each spoke
    3.

      Actual results:

      no firmware schemas are generated for SNO clusters hfs includes requested
settings, but not current settings detected during spoke deployment

      Expected results:

      firmwareschemas are generated for each SNO cluster hfs for each SNO cluster
includes requested settings and current settings detected during deployment

      Additional info:

      
note that despite the DNS names and cluster names of these spokes, they are
deployed as SNO

must-gather and other logs will be attached in a comment

              janders@redhat.com Jacob Anders
              rhn-support-dgonyier Dwaine Gonyier
              Jad Haj Yahya Jad Haj Yahya
              Tao Liu
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: