-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Change way to create a pod in test #128809
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Ayato Tokubi <atokubi@redhat.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bitoku The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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-sigs/prow repository. |
Hi @bitoku. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
/test |
@HirazawaUi: The
The following commands are available to trigger optional jobs:
Use
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-sigs/prow repository. |
/test pull-kubernetes-node-crio-e2e |
It seems that the existing test jobs do not cover the scenario of running these tests on crio. Do we need to add new crio-based test job for the tests in |
@@ -851,7 +851,7 @@ var _ = SIGDescribe("Pods", func() { | |||
ginkgo.By("Create set of pods") | |||
// create a set of pods in test namespace | |||
for _, podTestName := range podTestNames { | |||
_, err := f.ClientSet.CoreV1().Pods(f.Namespace.Name).Create(ctx, | |||
_ = podClient.Create(ctx, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can omit the return value _, just like other callers. I think go lint won't complain about it.
_ = podClient.Create(ctx, | |
podClient.Create(ctx, |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
This PR fixes local test failures for those tests:
"should delete a collection of pods"
"should run through the lifecycle of Pods and PodStatus"
"should patch a pod status"
with this kind of error.
Details
This happens because they don't use a client for pods, which assign node when creating a pod.
kubernetes/test/e2e/common/node/pods.go
Line 192 in 6ec421e
kubernetes/test/e2e/framework/pod/pod_client.go
Line 247 in 3d7d06e
Which issue(s) this PR fixes:
This will fix test failures in cri-o.
cri-o/cri-o#8668
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: