-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.14.0
-
No
-
3
-
OCP VE Sprint 238, OCP VE Sprint 239, OCP VE Sprint 240, OCP VE Sprint 241
-
4
-
False
-
-
-
Goal: Verify that once this feature is GA in conjunction with OCP 4.14 GA (synchronously?), the TechPreviewNoUpgrade flag is no longer required to enable this feature in ZTP siteconfigs to enable WLP.
Original Description of problem:
Users of GitOps ZTP can't enable workload partitioning on multinode clusters. There are two components to enabling: 1. Extending SiteConfig CR with cpuPartitioningMode field -- A workaround would be to explicitly include the cpuPartitioningMode in the SiteConfig.spec.clusters[].installConfigOverrides field. 2. Enable passthrough of cpuPartitioningMode from AgentClusterInstall agent-install.openshift.io/install-config-overrides annotation.
Version-Release number of selected component (if applicable):
4.13.z
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- is blocked by
-
OCPBUGS-13310 [infrastructure-operator] GitOps ZTP does not support enabling multi-node workload partitioning
- Verified
- is related to
-
OCPBUGS-13301 GitOps ZTP does not support enabling multi-node workload partitioning
- Closed
-
OCPBUGS-13313 [release-4.13] GitOps ZTP does not support enabling multi-node workload partitioning
- Closed
- relates to
-
OCPBUGS-13148 cgroupv1 support for cpu balancing is broken for non-SNO nodes
- Closed
- links to
-
RHBA-2023:6837 OpenShift Container Platform 4.14.z bug fix update