-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
4.17.z, 4.18
-
Moderate
-
None
-
CNF RAN Sprint 257
-
1
-
Rejected
-
False
-
-
A fix has been proposed.
-
Description of problem:
When deployment a SNO spoke with Telco DU profile, the spoke completes deployment despite the BIOS profile containing at least one setting value that is not in the firmware schema enumeration for that setting
Version-Release number of selected component (if applicable):
OCP 4.17.0-0.nightly-2024-08-08-013133 ztp-site-generate v4.17.0-13 topology-aware-lifecycle-manager-operator-bundle-container-rhel9/images/v4.17.0-19 ACM v2.11.2-7
How reproducible:
always
Steps to Reproduce:
1. Deploy SNO spoke with Telco DU profile and cluster or node level BIOS profile supplied. 2. Observe deployment and logs/events 3.
Actual results:
deployment progresses to success
Expected results:
deployment should be blocked/prevented from progressing
Additional info:
Site config snippet apiVersion: ran.openshift.io/v1 kind: SiteConfig metadata: name: "site-plan-helix55" namespace: "helix55" spec: baseDomain: "lab.eng.rdu2.redhat.com" pullSecretRef: name: "helix55-pull-secret" clusterImageSetNameRef: "4.17" #biosConfigRef: # filePath: "./bios-profiles/bios-site.profile" clusters: - clusterName: "helix55" networkType: "OVNKubernetes" installConfigOverrides: "{\"capabilities\":{\"baselineCapabilitySet\": \"None\", \"additionalEnabledCapabilities\": [ \"NodeTuning\", \"OperatorLifecycleManager\", \"Ingress\" ] }}" cpuPartitioningMode: AllNodes extraManifestPath: sno-extra-manifest/ #extraManifests: # filter: # exclude: # - enable-cgroups-v1.yaml clusterType: sno clusterProfile: du biosConfigRef: filePath: "./bios-profiles/bios-cluster.profile" --- #bios-cluster.profile # ProcCIE value is not a valid enumeration of the setting. BootMode: Uefi EnergyEfficientTurbo: Disabled ProcTurboMode: Enabled ProcPwrPerf: OsDbpm ProcC1E: WrongValue ProcCStates: Enabled ProcVirtualization: Enabled
must-gather and other logs will be added in a comment.