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

Error: OCI runtime error: writing file /sys/fs/cgroup/...cut.../cgroup.procs: Device or resource busy #11165

Closed
cevich opened this issue Aug 9, 2021 · 4 comments
Assignees
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

@cevich
Copy link
Member

cevich commented Aug 9, 2021

/kind bug

Description

While updating images, noted newly persistent failures in the Podman run with --cgroup-parent [It] always honor --cgroup-parent CI test (test/e2e/run_cgroup_parent_test.go:102). @giuseppe attempted to fix this with #11068 but the test still regularly fails on F34 in rootless mode.

Steps to reproduce the issue:

  1. Execute rootless F34 integration tests using F34 VM image tagged c4815129062670336

Describe the results you received:

(Annotated test log)

...cut...
Running: podman [options] --cgroup-manager=cgroupfs run -d --cgroup-parent=/user.slice/user-21779.slice/[email protected]/user.slice/libpod-4274abfa8f436d00de9c93300cb9f5db6a75ff1f33161789485ccceda1570892.scope quay.io/libpod/fedora-minimal:latest sleep 100
         Error: OCI runtime error: writing file `/sys/fs/cgroup/user.slice/user-21779.slice/[email protected]/user.slice/libpod-4274abfa8f436d00de9c93300cb9f5db6a75ff1f33161789485ccceda1570892.scope/cgroup.procs`: Device or resource busy

Describe the results you expected:

All CI Tests should consistently pass

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Built from upstream/main commit 04ab2b1

Output of podman info --debug:

See Annotated test log link above

Package info (e.g. output of rpm -q podman or apt list podman):

See Annotated test log link above

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

int podman fedora-34 rootless host

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 9, 2021
cevich added a commit to cevich/podman that referenced this issue Aug 9, 2021
cevich added a commit to cevich/podman that referenced this issue Aug 17, 2021
@github-actions
Copy link

github-actions bot commented Sep 9, 2021

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Sep 9, 2021

@cevich any update?

@rhatdan
Copy link
Member

rhatdan commented Sep 9, 2021

@giuseppe Update?

@cevich
Copy link
Member Author

cevich commented Sep 9, 2021

The test is still being universally skipped w/ ref. to this issue.

mheon pushed a commit to mheon/libpod that referenced this issue Sep 16, 2021
and fix it for running with runc.

Closes: containers#11165

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.
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

No branches or pull requests

3 participants