You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we describe pod with pipelined state, we will find that events of the pod are empty. This will cause the illusion of scheduler exception.
After a scheduled round is over, if a pod is still in the pipelined state, the scheduler needs to report Unschedulable events for it, since in this scenario, the pod has not been successfully scheduled.
The text was updated successfully, but these errors were encountered:
sivanzcw
changed the title
pod with Pipelined status does not have events, actually the pod have not been bound to node
Pod with pipelined status does not have events, actually the pod have not been bound to node
Nov 3, 2019
If we describe pod with
pipelined
state, we will find that events of the pod are empty. This will cause the illusion of scheduler exception.After a scheduled round is over, if a pod is still in the
pipelined
state, the scheduler needs to reportUnschedulable
events for it, since in this scenario, the pod has not been successfully scheduled.The text was updated successfully, but these errors were encountered: