-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.17.0
-
Important
-
No
-
Proposed
-
False
-
-
Description of problem:
Unable to deploy Performance Profile on hypershift environment. [root@helix34 workspace]# oc get nodes NAME STATUS ROLES AGE VERSION foobar1-node-0 Ready worker 94m v1.30.2 foobar1-node-1 Ready,SchedulingDisabled worker 94m v1.30.2
Version-Release number of selected component (if applicable):
4.17.0-0.nightly-2024-07-24-055449
How reproducible:
Everytime
Steps to Reproduce:
1. Create a Mgmt and Hosted cluster 2. Apply the config map as show below: 3. One of the node in hosted Cluster is in "Ready SchedulingDisabled" state
Actual results:
One of the hosted cluster node is in Ready Scheduling Disabled mode: [root@helix34 workspace]# oc get nodes NAME STATUS ROLES AGE VERSION foobar1-node-0 Ready worker 77m v1.30.2 foobar1-node-1 Ready,SchedulingDisabled worker 77m v1.30.2
Expected results:
Performance Profile should be applied successfully
Additional info:
[root@helix34 workspace]# oc get cm/pp1 -o yaml apiVersion: v1 data: tuning: | apiVersion: performance.openshift.io/v2 kind: PerformanceProfile metadata: name: pp1 spec: cpu: isolated: 1,3-11,13,15-23 reserved: 0,2,12,14 nodeSelector: node-role.kubernetes.io/woker: "" numa: topologyPolicy: single-numa-node realTimeKernel: enabled: false workloadHints: highPowerConsumption: true realTime: true kind: ConfigMap metadata: creationTimestamp: "2024-07-24T09:15:46Z" name: pp1 namespace: clusters resourceVersion: "89888" uid: 16e1f44a-dfda-4c9f-9575-c777ce06f294