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

CNO YAML generation fails with operator: Exists tolerations in HostedCluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.17.z, 4.16.z, 4.18.z, 4.19.z
    • Networking / cluster-network-operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Rejected
    • None
    • In Progress
    • Bug Fix
    • Hide
        Issue: Fixed a bug where HostedCluster deployments would fail to complete network operator rollout when using tolerations with
        operator: Exists without specifying key or value fields.

        Impact: HostedClusters configured with tolerations like operator: Exists (which is valid Kubernetes syntax for tolerating all taints)
         would get stuck during deployment because the Cluster Network Operator failed to render valid YAML for the
        multus-admission-controller component.

        Resolution: Corrected the toleration YAML generation logic in the CNO to properly handle operator: Exists tolerations. The fix
        ensures that:
        - Tolerations with operator: Exists generate valid YAML without breaking on null values
        - Empty string values are still properly filtered out as intended
        - All standard toleration configurations continue to work as expected
      Show
        Issue: Fixed a bug where HostedCluster deployments would fail to complete network operator rollout when using tolerations with   operator: Exists without specifying key or value fields.   Impact: HostedClusters configured with tolerations like operator: Exists (which is valid Kubernetes syntax for tolerating all taints)    would get stuck during deployment because the Cluster Network Operator failed to render valid YAML for the   multus-admission-controller component.   Resolution: Corrected the toleration YAML generation logic in the CNO to properly handle operator: Exists tolerations. The fix   ensures that:   - Tolerations with operator: Exists generate valid YAML without breaking on null values   - Empty string values are still properly filtered out as intended   - All standard toleration configurations continue to work as expected
    • 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

       

              cewong@redhat.com Cesar Wong
              cewong@redhat.com Cesar Wong
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: