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

oc adm must-gather with --node-name picking a worker is never scheduled

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • Unspecified
    • QA
    • None
    • Rejected
    • None
    • In Progress
    • Bug Fix
    • Hide
      Before this fix it was impossible to schedule a must-gather pod to a specific worker node when --node-name argument was used as the pod's node affinity was accepting only control plane nodes. Now, the oc adm must-gather logic is updated to avoid setting node affinity when --node-name argument is set.
      Show
      Before this fix it was impossible to schedule a must-gather pod to a specific worker node when --node-name argument was used as the pod's node affinity was accepting only control plane nodes. Now, the oc adm must-gather logic is updated to avoid setting node affinity when --node-name argument is set.
    • None
    • None
    • None
    • None

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

      Description of problem:

      We, on openshift-virtualization, are running this command:

      oc adm must-gather --dest-dir=./tests-collected-info/must_gather_scope_module/collected_vm_gather_from_vm_node --image=registry.redhat.io/container-native-virtualization/cnv-must-gather-rhel9@sha256:13425c8ab8b4c584c8666d938ab677dbf1a584aad1e0c4a9cb7c44c027a8cefa --node-name=c01-hmeir421-fn6lh-worker-0-nrnpc -- /usr/bin/gather  --vms_details 

      and the pod is never scheduled because the nodeName and the affinity definitions on the must-gather pod spec are mutually exclusive.

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

      $ oc version
      Client Version: 4.21.0-ec.2
      Kustomize Version: v5.6.0
      Server Version: 4.21.0-ec.2
      Kubernetes Version: v1.34.1     

      How reproducible:

      Always
          

      Actual results:

      the must-gather pod is never scheduled

      Expected results:

      the must-gather pod is run on the node selected through --node-name     

      Additional info:

      must-gather pod details attached    

              aos-workloads-staff Workloads Team Bot Account
              rlobillo Ramón Lobillo
              None
              None
              Ying Zhou Ying Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: