-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17.z, 4.16.z, 4.18.z, 4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
In Progress
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
CNO fails to render multus-admission-controller control plane components when HostedCluster includes tolerations with - operator: Exists (without key/value specified). This prevents the network operator from completing rollout and HostedCluster from becoming available.
Version-Release number of selected component (if applicable):
OpenShift 4.18.19 (likely affects all versions) Cluster Network Operator HyperShift HostedCluster
How reproducible:
Always
Steps to Reproduce:
1. Create a HostedCluster with single toleration with no key/value: spec: tolerations: - operator: Exists 2. Wait for the HostedCluster to be created 3. Observe the network operator rollout status
Actual results:
HostedCluster never gets available nodes because the network operator never finishes rolling out. CNO fails to generate valid YAML for the multus-admission-controller control plane component.
Expected results:
HostedCluster should roll out successfully with operator: Exists tolerations, as this is valid Kubernetes toleration syntax.
Additional info:
- Issue occurs specifically with tolerations using operator: Exists without key/value - Workaround: specify tolerations with operator, key, and value - these work correctly - Problem appears to be in CNO's YAML generation/rendering logic for multus-admission-controller - Affects HostedCluster availability and network functionality