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

Adding Windows node to OCP cluster causing a taint from the cloud controller manager as uninitialized

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.16.0
    • 4.14.z
    • Windows Containers
    • None
    • Important
    • No
    • 0
    • WINC - Sprint 254, WINC - Sprint 255
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, because of a missing DNS suffix in the kubelet hostname on instances that are part of a Windows AD domain controller, the cloud provider failed to find VMs by name. This fix includes the DNS suffix in the hostname resolution. As a resuilt, the WMCO is able to configure and join Windows instances that are part of AD domain controller. (link:https://issues.redhat.com/browse/OCPBUGS-34758[*OCPBUGS-34758*])
      Show
      Previously, because of a missing DNS suffix in the kubelet hostname on instances that are part of a Windows AD domain controller, the cloud provider failed to find VMs by name. This fix includes the DNS suffix in the hostname resolution. As a resuilt, the WMCO is able to configure and join Windows instances that are part of AD domain controller. (link: https://issues.redhat.com/browse/OCPBUGS-34758 [* OCPBUGS-34758 *])
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-33319. The following is the description of the original issue:
      —
      Description of problem:

      We followed the documentation for bringing your own Windows host (BYOH) into an existing OpenShift cluster 4.14.X running in vsphere. We were able to join the node to the cluster and schedule a Windows workload. But adding a Windows node is causing a taint node.cloudprovide.kubernetes.io=uninitilized and also the VSphereCSIDriverOperatorCRUpgradeable: VMwareVSphereControllerUpgradeable: unable to find VM win-worker-1 by UUID


Customert support case https://access.redhat.com/support/cases/#/case/03810909. I have attached oc-must gather, and the rest of details from the cluster.

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

      OCP 4.14.X and WMCO 9.0.X

      How reproducible:

       Follow the docs https://docs.openshift.com/container-platform/4.14/windows_containers/byoh-windows-instance.html  

      Actual results:

      Taint: node.cloudprovide.kubernetes.io=uninitilized

VMwareVSphereControllerUpgradeable: unable to find VM win-worker-1 by UUID

       

      QE:

            jvaldes@redhat.com Jose Valdes
            openshift-crt-jira-prow OpenShift Prow Bot
            Aharon Rasouli Aharon Rasouli
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: