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
fix conflict hostPort e2e test #99112
fix conflict hostPort e2e test #99112
Conversation
@JornShen: 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. |
/cc @aojea |
/retest |
a10610c
to
8502eb7
Compare
updated. @aojea |
/lgtm |
/test pull-kubernetes-conformance-kind-ga-only-parallel |
@aojea in what way? seems to me this is functionally from a conformance POV is equivilant? |
8502eb7
to
6b8781c
Compare
updated. |
Bad wording, just wanted to say that touches a conformance test to give the pr my priority, not meaning it changes it behaviour sorry |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JornShen, oomichi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
/kind flake
/kind failing-test
What this PR does / why we need it:
fix network test: [sig-network] HostPort validates that there is no conflict between pods with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]
failed link:
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-e2e-kind-ipv6
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/99098/pull-kubernetes-e2e-kind-ipv6/1361354037437403136/
From the logs of kubelet. pod create no success. The test go through it checking pod no pending.
I think it is no enough to support the following test check.
Does this PR introduce a user-facing change?