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

Too restrictive nodeAffinity when SR-IOV is deployed on Hypershift Nodepools

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18.0
    • Networking / SR-IOV
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      SR-IOV network operator pods won't deploy when installed on Hypershift node pools.

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

      4.18.0

      How reproducible:

      Deploy an Hypershift HostedCluster with CNF ready Nodepools (SR-IOV compatible network device, etc). The SR-IOV Network operator pods won't deploy.

      Actual results:

      The pods won't schedule: https://paste.opendev.org/show/bsOI1jVC1QqBhEcvKGvc/

      Expected results:

      The pods should be able to schedule.

      Additional info:

      The problem is that node affinity is too strict for Hypershift: https://github.com/openshift/sriov-network-operator/blob/45f22daa4ca8fb10f64e280d0aa2b7925da717d7/deploy/operator.yaml#L22C9-L30

      The Nodepool have no idea of their control plane/masters nodes so this rule will make the pods unschedulable.

       

              emacchi@redhat.com Emilien Macchi
              emacchi@redhat.com Emilien Macchi
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: