Skip to content
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

[CI][TEST] investigate https://github.com/containers/storage/issues/2042 #23516

Closed
wants to merge 3 commits into from

Conversation

giuseppe
Copy link
Member

@giuseppe giuseppe commented Aug 6, 2024

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 6, 2024
Copy link
Contributor

openshift-ci bot commented Aug 6, 2024

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@openshift-ci openshift-ci bot added the do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None label Aug 6, 2024
Copy link
Contributor

openshift-ci bot commented Aug 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe

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 /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 Aug 6, 2024
@giuseppe giuseppe force-pushed the ci-flake-investigate branch 9 times, most recently from 23ef176 to 8ae2f4e Compare August 6, 2024 15:45
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 6, 2024
@giuseppe giuseppe force-pushed the ci-flake-investigate branch from 8ae2f4e to dde9ca7 Compare August 7, 2024 07:31
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 7, 2024
@giuseppe giuseppe force-pushed the ci-flake-investigate branch 2 times, most recently from be7995f to f99d874 Compare August 7, 2024 10:52
@giuseppe
Copy link
Member Author

giuseppe commented Aug 7, 2024

@Luap99 should we ignore ENOENT for the following error (seen here https://api.cirrus-ci.com/v1/task/5568058947796992/logs/main.log)?

[+0235s]       <string>: time="2024-08-07T06:12:00-05:00" level=error msg="IPAM error: failed to get ips for container ID 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244 on network podman" time="2024-08-07T06:12:00-05:00" level=error msg="IPAM error: failed to find ip for subnet 10.88.0.0/16 on network podman" time="2024-08-07T06:12:00-05:00" level=error msg="netavark: open container netns: open /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: IO error: No such file or directory (os error 2)" time="2024-08-07T06:12:00-05:00" level=error msg="Unable to clean up network for container 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244: \"unmounting network namespace for container 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244: failed to remove ns path: remove /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: no such file or directory, failed to unmount NS: at /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: no such file or directory\""

@giuseppe giuseppe force-pushed the ci-flake-investigate branch from f99d874 to ebf3cfa Compare August 7, 2024 11:59
@edsantiago
Copy link
Member

@giuseppe that looks like #19721 which is possibly our number one flake right now

@Luap99
Copy link
Member

Luap99 commented Aug 7, 2024

@Luap99 should we ignore ENOENT for the following error (seen here https://api.cirrus-ci.com/v1/task/5568058947796992/logs/main.log)?

[+0235s]       <string>: time="2024-08-07T06:12:00-05:00" level=error msg="IPAM error: failed to get ips for container ID 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244 on network podman" time="2024-08-07T06:12:00-05:00" level=error msg="IPAM error: failed to find ip for subnet 10.88.0.0/16 on network podman" time="2024-08-07T06:12:00-05:00" level=error msg="netavark: open container netns: open /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: IO error: No such file or directory (os error 2)" time="2024-08-07T06:12:00-05:00" level=error msg="Unable to clean up network for container 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244: \"unmounting network namespace for container 054cecd4e6cddb94eba8c3439e3409cfa2592ca14d8355d2d68fbbfd8d8eb244: failed to remove ns path: remove /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: no such file or directory, failed to unmount NS: at /run/netns/netns-bbc7dc90-abc2-c310-b4a4-99d81927be34: no such file or directory\""

I am already debugging this, for unmount and remove yes: containers/common#2112. But I am still not decided on the other errors.

@giuseppe giuseppe force-pushed the ci-flake-investigate branch 4 times, most recently from 8ef0329 to 278626b Compare August 7, 2024 14:15
@giuseppe giuseppe closed this Aug 7, 2024
@giuseppe giuseppe reopened this Aug 8, 2024
@giuseppe giuseppe force-pushed the ci-flake-investigate branch from 278626b to 5d544eb Compare August 8, 2024 08:31
@giuseppe giuseppe force-pushed the ci-flake-investigate branch 2 times, most recently from 741f349 to ac53a36 Compare August 8, 2024 09:56
Signed-off-by: Giuseppe Scrivano <[email protected]>
Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe force-pushed the ci-flake-investigate branch 3 times, most recently from d834b89 to cea2bdf Compare August 8, 2024 11:54
Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe force-pushed the ci-flake-investigate branch from cea2bdf to b1cdc3d Compare August 8, 2024 14:10
@giuseppe giuseppe closed this Aug 8, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Nov 7, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Nov 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/release-note-label-needed Enforce release-note requirement, even if just None do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants