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

With two (gpu) autoscalers defined, OCP is scaling up the bigger one even though the smaller one would've been enough

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • None
    • 4.11
    • Cluster Autoscaler
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      On a cluster with two autoscalers defined (one with node flavour p3.8xlarge - 4 gpus per node - and one with node flavour g4dn.xlarge - 1 gpu per node-) I've tried to trigger a scale up by requesting 1 GPU.
      The node that was scaled up was the multi-gpu one (p3.8xlarge) even though the smaller variant would've been enough to satisfy my request.

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

      OCP 4.11

      How reproducible:

      Always in my testing

      Steps to Reproduce:

      1.Define two autoscalers, in my case one with single-gpu nodes and one with multi-gpu nodes
      2. Try to trigger a scale up by requesting 1 gpu
      

      Actual results:

      multi-gpu node is scaled up to fulfill my request of 1 gpu

      Expected results:

      single-gpu node should've been scaled up, since that would've fulfilled my request

      Additional info:

       

              mimccune@redhat.com Michael McCune
              rhn-support-lgiorgi Luca Giorgi
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: