Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Focus failing e2e test #5924

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.

Sign up for GitHub

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

Jump to bottom
Closed
saschagrunert wants to merge 1 commit into from
Closed

Focus failing e2e test #5924

saschagrunert wants to merge 1 commit into from

Conversation

@saschagrunert
Copy link
Member

@saschagrunert saschagrunert commented Jun 1, 2022

What type of PR is this?

/kind failing-test

What this PR does / why we need it:

Debugging #5923 by focusing the single test case and inspecting the kubelet logs.

Which issue(s) this PR fixes:

Refers to #5923

Special notes for your reviewer:

/hold

Nothing we should merge.

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jun 1, 2022
@openshift-ci openshift-ci bot requested review from QiWang19 and wgahnagl June 1, 2022 08:39
@openshift-ci openshift-ci bot added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jun 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 1, 2022
@aojea
Copy link
Contributor

aojea commented Jun 1, 2022

/cc

@openshift-ci openshift-ci bot requested a review from aojea June 1, 2022 08:49
@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 1, 2022

From test_pull_request_crio_e2e_crun_fedora:

e2e logs: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-federated-results/pr-logs/pull/cri-o_cri-o/5924/test_pull_request_crio_e2e_crun_fedora/18155/artifacts/e2e.log

Kubelet logs: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-federated-results/pr-logs/pull/cri-o_cri-o/5924/test_pull_request_crio_e2e_crun_fedora/18155/artifacts/kubelet.log

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 1, 2022 •
edited
Loading

It looks like that the pod status it not being correctly updated. 🤔 (May be a bug in the forced CRI stats provider, but it works with both on my local machine)

@aojea
Copy link
Contributor

aojea commented Jun 1, 2022

It looks like that the pod status it not being correctly updated. thinking (May be a bug in the forced CRI stats provider)

we have plenty of those things these days in k/k 😄 ... but why it didn't happen in the upstream CI?

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 1, 2022 •
edited
Loading

It looks like that the pod status it not being correctly updated. thinking (May be a bug in the forced CRI stats provider)

we have plenty of those things these days in k/k smile ... but why it didn't happen in the upstream CI?

I think we do not run this test upstream with CRI-O, it also seems to occur only in our CI config since I'm not able to reproduce locally with the same settings.

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 1, 2022

/retest

1 similar comment
@haircommander
Copy link
Member

haircommander commented Jun 1, 2022

/retest

@haircommander haircommander mentioned this pull request Jun 1, 2022
Merged
TomSweeneyRedHat
TomSweeneyRedHat reviewed Jun 1, 2022
View reviewed changes
contrib/test/integration/build/kubernetes.yml
- name: clone kubernetes source repo
git:
repo: "https://github.com/{{ k8s_github_fork }}/kubernetes.git"
repo: "https://github.com/saschagrunert/kubernetes.git"
Copy link
Contributor

@TomSweeneyRedHat TomSweeneyRedHat Jun 1, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would probably be better grabbed from a public repo....

@TomSweeneyRedHat
Copy link
Contributor

TomSweeneyRedHat commented Jun 1, 2022

One comment, otherwise LGTM

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 2, 2022

/retest

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 2, 2022

/retest

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 2, 2022

@saschagrunert: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/kata-jenkins b327e70 link true /test kata-containers
Details

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. I understand the commands that are listed here.

@saschagrunert
Copy link
Member Author

saschagrunert commented Jun 2, 2022

/test e2e_fedora

@saschagrunert
Focus failing e2e test
a7a81c6 
Signed-off-by: Sascha Grunert <[email protected]>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 2, 2022

@saschagrunert: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp b327e70 link true /test e2e-gcp
ci/prow/e2e-agnostic b327e70 link true /test e2e-agnostic
ci/kata-jenkins b327e70 link true /test kata-containers
ci/openshift-jenkins/e2e_crun a7a81c6 link true /test e2e_crun
ci/openshift-jenkins/e2e_fedora a7a81c6 link true /test e2e_fedora
ci/openshift-jenkins/integration_crun_cgroupv2 a7a81c6 link false /test integration_cgroupv2
ci/openshift-jenkins/e2e_crun_cgroupv2 a7a81c6 link false /test e2e_cgroupv2

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@saschagrunert saschagrunert deleted the debug branch June 23, 2022 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mrunalp mrunalp Awaiting requested review from mrunalp mrunalp is a code owner

@runcom runcom Awaiting requested review from runcom

@QiWang19 QiWang19 Awaiting requested review from QiWang19

@wgahnagl wgahnagl Awaiting requested review from wgahnagl

@aojea aojea Awaiting requested review from aojea

1 more reviewer

@TomSweeneyRedHat TomSweeneyRedHat TomSweeneyRedHat left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@saschagrunert @aojea @haircommander @TomSweeneyRedHat @openshift-ci-robot