![]() Automatic merge from submit-queue Fix node confomance test Fixes https://github.com/kubernetes/kubernetes/issues/28255, https://github.com/kubernetes/kubernetes/issues/28250, https://github.com/kubernetes/kubernetes/issues/28341. The main reason of the flake is that in the failed test expects the `PodPhase` to keep `Pending`. It did `Eventually` check and `Consistently` check for 5 seconds. However, the default `PodPhase` is `Pending`, when the check passes, the `PodStatus` could still be in default state. After that, the test expects the container status to be `Waiting`, which may not be the case, because the default `ContainerStatuses` is empty, and the pod could still be in the default state. This PR changes the test to ensure `ContainerStatuses` first and then check the `PodPhase` after that. Mark P1 because the test fails relatively frequently and does block some PRs. @pwittrock /cc @liangchenye @ncdc []() |
||
---|---|---|
.. | ||
environment | ||
jenkins | ||
runner | ||
configmap.go | ||
container_list.go | ||
container_manager_test.go | ||
container.go | ||
doc.go | ||
downward_api_test.go | ||
e2e_build.go | ||
e2e_node_suite_test.go | ||
e2e_remote.go | ||
e2e_service.go | ||
exec_util.go | ||
image_conformance_test.go | ||
image.go | ||
kubelet_test.go | ||
mirror_pod_test.go | ||
OWNERS | ||
privileged_test.go | ||
README.md | ||
runtime_conformance_test.go | ||
util.go |
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.1/docs/devel/collab.md).Documentation for other releases can be found at releases.k8s.io.
See e2e-node-tests