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
in the #3498 , we support updating NominatedNodeName for pipelined task
now we met one situation, the kube-scheduler and volcano's behaviour is not same
Steps to reproduce the issue
create a cluster with one 1C1G node
create a pod A, which request 1C1G, with the preStop command sleep 600
after the pod A is running, delete it. the pod A will be terminating in 10 minutes
create a pod B with request 1C1G, and it will be pending
Describe the results you received and expected
expected:
same as the kube-schduler, mark the pending pod as unschedulable and will not update its nominatedNodeName field
received:
mark the pending pod as unschedulable and update its nominatedNodeName field
What version of Volcano are you using?
latest
Any other relevant information
No response
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Description
in the #3498 , we support updating NominatedNodeName for pipelined task
now we met one situation, the kube-scheduler and volcano's behaviour is not same
Steps to reproduce the issue
Describe the results you received and expected
expected:
same as the kube-schduler, mark the pending pod as unschedulable and will not update its nominatedNodeName field
received:
mark the pending pod as unschedulable and update its nominatedNodeName field
What version of Volcano are you using?
latest
Any other relevant information
No response
The text was updated successfully, but these errors were encountered: