kubernetes: Test Failure: Conformance test to validate there is no conflict between pods with same hostPort but different hostIP and protocol

What happened?

The below test is failing in our daily conformance runs that test the suite against the latest k8s cluster: Test that validates that there is no conflict between pods with same hostPort but different hostIP and protocol https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/hostport.go#L61

Please look at https://k8s-testgrid.appspot.com/sig-node-ppc64le#conformance Sample failure run https://prow.k8s.io/view/gs/ppc64le-kubernetes/logs/periodic-kubernetes-conformance-test-ppc64le/1457992350935552000

What did you expect to happen?

The test should pass as in earlier builds.

How can we reproduce it (as minimally and precisely as possible)?

Based on your deployer, you may focus and run the conformance test as mentioned in https://github.com/kubernetes-sigs/kubetest2#usage

Kubernetes version

Started failing from K8s Build version : v1.23.0-alpha.4.185+97125e76f3a7a3

Cloud provider

We observed this on k8s cluster that is on PowerVS (IBM)

OS version

CentOS 8.4 Architecture: ppc64le

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 17 (17 by maintainers)

Most upvoted comments

it is not a regression https://github.com/kubernetes/kubernetes/issues/106264#issuecomment-964207939 , or at least there is no evidence of that.

Somebody has to run that test on that environment and check the logs, and figure out why the pod readiness probe is failing, there are multiple reasons why this can happen , and not all of them are related to kubernetes …

aojea on Nov 12, 2021

This test cluster appears to have a single node. It is not a valid candidate for conformance testing.

https://github.com/kubernetes/kubernetes/issues/106303#issuecomment-965608855

https://groups.google.com/g/kubernetes-sig-architecture/c/s-SCpQQDOEo/m/FUGmTFKKAQAJ

From the job logs:

‘–focus-regex=[Conformance]’ ‘–skip-regex=[Disruptive]|[Serial]’

This is not conformance, conformance must have no skips. Please rename the job or remove the skip.

FYI you are uploading the kubectl binary in ARTIFACTS which is probably unintentional and wasting a lot of storage? 🙃

Thanks for the feedback, will fix these comments…

mkumatag on Nov 11, 2021