-
Notifications
You must be signed in to change notification settings - Fork 701
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
Kubeadm: unit tests failed on server with multiple CRI endpoints #2863
Comments
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. 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. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/transfer kubeadm |
makes sense to fix this. thanks for logging the issue. we need to pass a predefined CRI endpoint in an InitConfiguration. /help |
@neolit123: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
Seems like this issue can be closed. /close |
@liangyuanpeng: You can't close an active issue/PR unless you authored it or you are a collaborator. 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. |
No, we still need to fix the remaining cases. |
/assign Let me take care of rest of them. |
Which jobs are failing?
unit test
Which tests are failing?
They all failed with same errors:
Since when has it been failing?
Always
Testgrid link
No response
Reason for failure (if possible)
criSocket
is required forInitConfiguration
on server with multiple CRI endpoints, but in unit testcriSocket
is empty.Anything else we need to know?
No response
Relevant SIG(s)
/area kubeadm
The text was updated successfully, but these errors were encountered: