-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
packet_ubuntu20-calico-aio is failing on the task "packet-ci : Wait for vms to have ipaddress assigned" #8786
Comments
packet-ci : Wait for vms to have ipaddress assigned
This seems solved already. |
This issue still seems to exist:
@oomichi @floryut @yankay @MrFreezeex Some advice would be greatly appreciated🙏 |
/reopen |
@ErikJiang: Reopened this issue. In response to this:
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. |
I have a theory for that failure: under resource contention, some jobs which provision kubevirt VMs before executing kubespray on it (packet*) fight for resource allocation: Thus we get in some sort of livelock. @floryut Does that seems plausible to you ? Could you look at the cluster during a CI runs to confirm that theory ? If that's the case, there is the Coscheduler plugin which could help us, but that's rather involved, so let's confirm first... EDIT: |
/close |
@VannTen: Closing this issue. In response to this:
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. |
looks like VM can't be scheduled. |
Which jobs are failing:
packet_ubuntu20-calico-aio
Which test(s) are failing:
the task
packet-ci : Wait for vms to have ipaddress assigned
Since when has it been failing:
5/4/2022
Testgrid link:
https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/2413816664
Reason for failure:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: