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

Pods pointing to non-existing scheduler are in Pending status with no events

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.15, 4.16, 4.17, 4.18, 4.19, 4.20, 4.21
    • kube-scheduler
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a pod has the schedulerName value set to a non-existing scheduler, the pod will be created and stuck on "Pending" indefinitely with no additional information.

      There will not be any event nor log in the entire cluster warning about this issue.

       

      Expected result:

      Having an event on the pod namespace that warns of the wrong schedulerName assigned to the pod each time the pod tries to be scheduled, and also logs in the kube-scheduler pod warning about the wrong schedulerName configured.

       

      KCS explaining that : https://access.redhat.com/solutions/4652171

              rh-ee-jujohn Jubitta John
              rhn-support-parodrig Pablo Rodriguez Guillamon
              None
              None
              Rama Kasturi Narra Rama Kasturi Narra
              None
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: