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

WMCO is unable to drain DaemonSet workloads

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.12.z
    • 4.13
    • Windows Containers
    • None
    • No
    • 0
    • WINC - Sprint 233
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release note captured through https://issues.redhat.com/browse/OCPBUGS-5354
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-5354. The following is the description of the original issue:

      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-mankulka Mansi Kulkarni
              openshift-crt-jira-prow OpenShift Prow Bot
              Aharon Rasouli Aharon Rasouli
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: