Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pod with pipelined status does not have events, actually the pod have not been bound to node #505

Closed
sivanzcw opened this issue Nov 3, 2019 · 0 comments · Fixed by #506

Comments

@sivanzcw
Copy link
Contributor

sivanzcw commented 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 report Unschedulable events for it, since in this scenario, the pod has not been successfully scheduled.

@sivanzcw 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant