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.

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

podman-remote wait: fails with open /proc/PID/cgroup: ENOENT #12457

Closed
edsantiago opened this issue Nov 30, 2021 · 2 comments · Fixed by #12464
Closed

podman-remote wait: fails with open /proc/PID/cgroup: ENOENT #12457

edsantiago opened this issue Nov 30, 2021 · 2 comments · Fixed by #12464
Assignees
@giuseppe
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

New podman-remote flake:

# # podman-remote [...] wait after_change_cnt
# Error: open /proc/66223/cgroup: no such file or directory
# [ rc=125 (** EXPECTED 0 **) ]

[sys] 166 podman export, alter tarball, re-import
@edsantiago edsantiago added flakes Flakes from Continuous Integration remote Problem is in podman-remote labels Nov 30, 2021
@edsantiago
Copy link
Member Author

One more:

Podman run [It] using journald for container with container log_tag

giuseppe added a commit to giuseppe/libpod that referenced this issue Dec 1, 2021
@giuseppe
container, cgroup: detect pid termination
0afaf78 
If the /proc/$PID/cgroup file doesn't exist, then it is likely the
container was terminated in the meanwhile so report ErrCtrStopped that
is already handled instead of ENOENT.

commit a66f40b introduced the regression.

Closes: containers#12457

[NO NEW TESTS NEEDED] it solves a race in the CI that is difficult to reproduce.

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe mentioned this issue Dec 1, 2021
Merged
@giuseppe
Copy link
Member

giuseppe commented Dec 1, 2021 •
edited
Loading

PR here: container, cgroup: detect pid termination #12464

mheon pushed a commit to mheon/libpod that referenced this issue Dec 6, 2021
@giuseppe @mheon
container, cgroup: detect pid termination
aa9799b 
If the /proc/$PID/cgroup file doesn't exist, then it is likely the
container was terminated in the meanwhile so report ErrCtrStopped that
is already handled instead of ENOENT.

commit a66f40b introduced the regression.

Closes: containers#12457

[NO NEW TESTS NEEDED] it solves a race in the CI that is difficult to reproduce.

Signed-off-by: Giuseppe Scrivano <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@giuseppe giuseppe

Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

container, cgroup: detect pid termination giuseppe/libpod
2 participants
@giuseppe @edsantiago