Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-5215

Can't start GPU Notebook on GPU node with taint

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • No
    • No
    • No
    • Pending
    • None

      Description of problem:

      After creating a GPU machine pool with a taint, RHODS doesn't recognize those nodes.

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Create machine pool with GPUs
      2. After a node is ready, go to the notebook spawner and check the gpu dropdown.
      3. As an additional check, navigate to /api/gpu

      Actual results:

      GPU selection is disabled

      /api/gpu returns 0

      Expected results:

      GPU selection is enabled with 1 available

      /api/gpu returns 1

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      quay.io/llasmith/rhods-operator-live-catalog:1.16.0-hotfix-2bf4eac

      Workaround:

      Do not put taints on GPU machine pools/nodes

      Additional info:

              Unassigned Unassigned
              cchase@redhat.com Chris Chase
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: