-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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/fedora] found more than one filter (2) attached to a cgroup #2976
Comments
Was this happening regularly, or is it a flaky issue? I don't see it in the CI for #2986 (where I added some debugging info to try to figure out what's going on here). |
OK, I think that was a flake, related to checkpoint/restore. The cause of it might be the container being restored into the same cgroup it was checkpointed from, which might not have been fully removed by the restore time. Now, why the cgroup was allegedly not removed is not clear to me. To debug, we can add a check that the cgroup is present before creating it. In fact, it might make sense to print a warning in such a case (except when a few containers are sharing the same cgroup... but there's no notion for it in runtime spec). Tried to reproduce this locally: $ cd libcontainer/integration
$ go test -c .
$ sudo ./integration.test -test.v -test.run Checkpoint -test.count 1200
=== RUN TestUsernsCheckpoint
--- PASS: TestUsernsCheckpoint (0.62s)
=== RUN TestCheckpoint
--- PASS: TestCheckpoint (0.49s)
=== RUN TestUsernsCheckpoint
--- PASS: TestUsernsCheckpoint (0.51s)
.... but it works just fine (i.e. I was not able to reproduce that). |
This might be different but I am seeing the same warning from the test added by #3000 |
I think the warning is coming from the the lack of |
This should be fixed by now. |
On GHA CI, Fedora:
I thought we'd never see this warning; looks suspicious to me.
The text was updated successfully, but these errors were encountered: