Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-28524

[2192858] kubevirt-job pod ignores node placement configuration

XMLWordPrintable

    • CNV Virtualization Sprint 236
    • High

      Description of problem:

      Add tolerations in node placement rules as per https://docs.openshift.com/container-platform/4.12/virt/install/virt-specifying-nodes-for-virtualization-components.html.

      These rules are not getting propagated to the kubevirt-xxx-jobxxx pod.

      When all nodes have taints set, the pod will be stuck in "Pending" status and virt-oprator will fail to deploy virt components.

      ~~~
      2023-05-02T17:48:15.692306010Z

      {"component":"virt-operator","kind":"","level":"error","msg":"Waiting on install strategy to be posted from job kubevirt-6dd2f5f71de2802413f34578306382b99a65c12f-jobk8c54","name":"kubevirt-6dd2f5f71de2802413f34578306382b99a65c12f-jobk8c54","namespace":"openshift-cnv","pos":"kubevirt.go:948","timestamp":"2023-05-02T17:48:15.692261Z","uid":"2a2df195-2806-4d1a-a5d6-f135f56f44bb"}

      ~~~

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

      OpenShift Virtualization 4.12.2

      How reproducible:

      100%

      Steps to Reproduce:

      1. Add node placement rules on hco object.
      2. Check the placement rules are applied to kubevirt-xxx-jobxxx pod.

      Actual results:

      kubevirt-job pod ignores node placement configuration

      Expected results:

      Node placement configuration should be propagated to kubevirt-job pod.

      Additional info:

      This looks to be already fixed upstream https://github.com/kubevirt/kubevirt/commit/166f5063d1cc839fa1811871418cc528e829ca94

            prnaraya@redhat.com Prita Narayan (Inactive)
            rhn-support-nashok Nijin Ashok
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: