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

WMCO is unable to drain DaemonSet workloads

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.13.0
    • 4.13
    • Windows Containers
    • None
    • 3
    • WINC - Sprint 230, WINC - Sprint 231
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the the Windows Machine Config Operator (WMCO) could not drain `DaemonSet` workloads. This issue caused Windows`DaemonSet` pods to block Windows nodes that the WMCO attempted to remove or upgrade. With this update, an WMCO includes additional role-based access control (RBAC) permisions, so that the WMCO can remove `DaemonSet` workloads. An WMCO can also delete any processes that were created with the containerd shim, so that `DaemonSet` containers do not exist on a Windows instance after a WMCO removes a node from a cluster. link:https://issues.redhat.com/browse/OCPBUGS-5354[*OCPBUGS-5354*])
      Show
      Previously, the the Windows Machine Config Operator (WMCO) could not drain `DaemonSet` workloads. This issue caused Windows`DaemonSet` pods to block Windows nodes that the WMCO attempted to remove or upgrade. With this update, an WMCO includes additional role-based access control (RBAC) permisions, so that the WMCO can remove `DaemonSet` workloads. An WMCO can also delete any processes that were created with the containerd shim, so that `DaemonSet` containers do not exist on a Windows instance after a WMCO removes a node from a cluster. link: https://issues.redhat.com/browse/OCPBUGS-5354 [* OCPBUGS-5354 *])
    • Bug Fix
    • Done

      Description of problem:

      When a DaemonSet targeting Windows nodes is on the cluster, WMCO is unable to drain affected nodes.
      

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

      
      

      How reproducible:

      Always
      

      Steps to Reproduce:

      1. Create a DaemonSet targeting Windows nodes
      2. Upgrade WMCO
      

      Actual results:

      error removing undesired nodes from cluster: unable to deconfigure instance with node ip-10-0-160-32.us-west-2.compute.internal: unable to drain node ip-10-0-160-32.us-west-2.compute.internal: cannot delete daemonsets.apps \"loki-promtail\" is forbidden: User \"system:serviceaccount:openshift-windows-machine-config-operator:windows-machine-config-operator\" cannot get resource \"daemonsets\" in API group \"apps\" in the namespace \"openshift-e2e-loki\": openshift-e2e-loki/loki-promtail-pcsnb"
      

      Expected results:

      No error
      

      Additional info:

      
      

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

              Created:
              Updated:
              Resolved: