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

Failed to add conmon to systemd sandbox cgroup: EEXIST #12535

Closed
edsantiago opened this issue Dec 7, 2021 · 2 comments · Fixed by #12538
Closed

Failed to add conmon to systemd sandbox cgroup: EEXIST #12535

edsantiago opened this issue Dec 7, 2021 · 2 comments · Fixed by #12538
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Seeing this pretty heavily on gating tests for the new f35 build (podman-3:3.4.3-1.fc35):

   # podman exec --user root 34858b5f0a8fd5c07c1a3e0ba1629a397fdfcd29715fe9255003556de52c82e4 adduser -u 4242 -G ping -D -g Aqx1Mf TygglerK -s /bin/sh newuser3
   time="2021-12-07T18:47:12-05:00" level=warning msg="Failed to add conmon to systemd sandbox cgroup: Unit libpod-conmon-34858b5f0a8fd5c07c1a3e0ba1629a397fdfcd29715fe9255003556de52c82e4.scope already exists."

Root. Lots and lots of failures. Seem to be only in exec.

@giuseppe PTAL when you get back from PTO. This is looking pretty urgent.

@edsantiago edsantiago added the kind/bug Categorizes issue or PR as related to a bug. label Dec 8, 2021
@edsantiago
Copy link
Member Author

Root only. I don't see it rootless. And, this isn't even a flake any more: it's 100%.

# podman run -d --name foo quay.io/libpod/testimage:20210610 top
2d02fdbc47549a1c08a6670fbd37958861a56cd7d330506df25e2bc5d24256ab
# podman exec foo date
WARN[0000] Failed to add conmon to systemd sandbox cgroup: Unit libpod-conmon-2d02fdbc47549a1c08a6670fbd37958861a56cd7d330506df25e2bc5d24256ab.scope already exists.

I can't find a way to not make it happen.

giuseppe added a commit to giuseppe/libpod that referenced this issue Dec 8, 2021
commit ee62711 introduced the
regression.

It was mistakenly removed as part of a cleanup, but this code is
needed by another code path, where we move conmon for the exec session
to the same cgroup used by conmon for the process.

Closes: containers#12535

[NO NEW TESTS NEEDED] it fixes a regression in the CI

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe
Copy link
Member

giuseppe commented Dec 8, 2021

PR here: #12538

edsantiago pushed a commit to edsantiago/libpod that referenced this issue Dec 8, 2021
commit ee62711 introduced the
regression.

It was mistakenly removed as part of a cleanup, but this code is
needed by another code path, where we move conmon for the exec session
to the same cgroup used by conmon for the process.

Closes: containers#12535

[NO NEW TESTS NEEDED] it fixes a regression in the CI

Signed-off-by: Giuseppe Scrivano <[email protected]>
@mheon mheon mentioned this issue Dec 8, 2021
@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.
Labels
kind/bug Categorizes issue or PR as related to a bug. 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 a pull request may close this issue.

2 participants