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

React to the removal of the CCM ClusterOperator condition 'CloudControllerOwner'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.16.0
    • 4.16.0
    • Windows Containers
    • None
    • Critical
    • No
    • 2
    • WINC - Sprint 251
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      On Azure clusters, WMCO would check if an external cloud controller was being used on the cluster, and if so would adjust configuration logic accordingly. The CCM use has been default since 4.15, and in 4.16 the status condition WMCO used to check for this has been removed. This caused WMCO to incorrectly assume that CCM was not in use. This has been fixed by removing the check, and always doing the required logic on Azure clusters.
      Show
      On Azure clusters, WMCO would check if an external cloud controller was being used on the cluster, and if so would adjust configuration logic accordingly. The CCM use has been default since 4.15, and in 4.16 the status condition WMCO used to check for this has been removed. This caused WMCO to incorrectly assume that CCM was not in use. This has been fixed by removing the check, and always doing the required logic on Azure clusters.
    • Bug Fix
    • In Progress

      Description of problem:

      The CloudControllerOwner condition is being removed from the CCM ClusterOperator.
https://github.com/openshift/cluster-cloud-controller-manager-operator/commit/65c07a6e44bfa1b0cdfadc264d3341c093ffd914

When this change makes it into the 4.16 payload, WMCO will no longer have to check for it when deciding configuration logic.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Always

      Steps to Reproduce:

          1. Configure a Windows Node on azure on a 4.16 cluster which includes the linked commit

      Actual results:

      The Node is not schedulable due to the taint node.cloudprovider.kubernetes.io/uninitialized

      Expected results:

      The Node is schedulable

      Additional info:

              rh-ee-ssoto Sebastian Soto
              rh-ee-ssoto Sebastian Soto
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: