-
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
centos-stream-9
CI is failing for the main branch
#3760
Comments
CI was passing for #3757 , but its merge commit into the main branch is failing 🤔 |
Tried updating from go 1.19 to go 1.20.2 as a hunch -- didn't work (see #3761). Looking into it. |
This comment was marked as outdated.
This comment was marked as outdated.
Apparently the reason is some issue in systemd v252-6.el9, and upgrading to the latest release (v252-8.el9 as of now) fixes the issue. Fixes: opencontainers#3760 Signed-off-by: Kir Kolyshkin <[email protected]>
Apparently the reason is some issue in systemd v252-6.el9, and upgrading to the latest release (v252-8.el9 as of now) fixes the issue. Fixes: opencontainers#3760 Signed-off-by: Kir Kolyshkin <[email protected]>
Apparently the reason is some issue in systemd v252-6.el9, and upgrading to the latest release (v252-8.el9 as of now) fixes the issue. Fixes: opencontainers#3760 Signed-off-by: Kir Kolyshkin <[email protected]>
OK, the issue is with systemd, sometimes it is working normally: [root@localhost runc-tst]# ./runc --systemd-cgroup run -d 444
[root@localhost runc-tst]# journalctl -b0 | grep 444
Mar 10 00:49:14 localhost systemd[1]: Started libcontainer container 444.
[root@localhost runc-tst]# ./runc list
ID PID STATUS BUNDLE CREATED OWNER
1234 0 stopped /home/runc-tst 2023-03-10T00:44:52.22112029Z root
444 102882 running /home/runc-tst 2023-03-10T00:49:14.558960612Z root
test_busybox 102815 running /home/runc-tst 2023-03-10T00:46:59.893227615Z root
[root@localhost runc-tst]# cat /proc/102882/cgroup
0::/system.slice/runc-444.scope
[root@localhost runc-tst]# jq '.cgroup_paths' < /run/runc/test_busybox/state.json
{
"": "/sys/fs/cgroup/system.slice/runc-test_busybox.scope"
} and sometimes systemd seems to ignore the request to create a scope, and the container process is not moved to a proper cgroup. [root@localhost runc-tst]# jq '.cgroup_paths' < /run/runc/444/state.json
{
"": "/sys/fs/cgroup/system.slice/runc-444.scope"
}
[root@localhost runc-tst]# cat /proc/102815/cgroup
0::/system.slice/google-startup-scripts.service |
OK I was not able to finish this investigation this week. Apparently, setting the cgroupPath in config.json helps, but I'm not sure why the defaults is not good enough (as they always worked before). For now, I removed the "required" setting for the centos-stream-9 test so we can still merge some PRs. Will continue working on that after a week . |
centos-stream-9 also fails for release-1.1 branch. |
So, what happens is
Here's an excerpt from the test with the added debug (
|
IOW, this smells like a systemd bug in CentOS Stream 9, because runc delete is called by the test and it does "stopUnit" call to systemd (which, somehow, is being ignored). The next step is to create a repro a file a bug to systemd. |
Ughm. There's a major bug in how runc handles creation of a systemd unit. I will file a bug. |
|
Fixed by #3782 |
https://cirrus-ci.com/task/5246167815028736 (6d0261c)
The text was updated successfully, but these errors were encountered: