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

make check' cannot run on master branch ("cgroupfs manager conmon cgroup should be 'pod' or empty") #24

Closed
vrubiolo opened this issue Nov 16, 2020 · 2 comments

Comments

@vrubiolo
Copy link

vrubiolo commented Nov 16, 2020

Hi there,

Not sure if this is the proper place to get help on the package here, feel free to let me know if there is a better place

I am trying to install and run crio-lxc and attempted to run the tests. This fails with the following fatal error when CRI-O checks the runtime configuration:

$ PACKAGES_DIR=/home/vrubiolo/Documents/Dev/repos/community/crio-lxc/packages/ make check 2>&1 | tee make_check_log.txt
[...]
not ok 1 basic cri-o workings
# (from function `crictl' in file test/helpers.bash, line 57,
#  in test file test/basic.bats, line 12)
#   `crictl runp test/basic-pod-config.json' failed
# time="2020-11-16T14:13:52+01:00" level=info msg="Starting CRI-O, version: 1.20.0-dev, git: f261f0560237c5c76a20db7f7c54214c026fe0e4(clean)"
# time="2020-11-16 14:13:52.233314056+01:00" level=info msg="Node configuration value for hugetlb cgroup is true"
# time="2020-11-16 14:13:52.233325596+01:00" level=info msg="Node configuration value for pid cgroup is true"
# time="2020-11-16 14:13:52.233433168+01:00" level=info msg="Node configuration value for memoryswap cgroup is true"
# time="2020-11-16 14:13:52.237398249+01:00" level=info msg="Node configuration value for systemd CollectMode is true"
# time="2020-11-16 14:13:52.237852416+01:00" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
# time="2020-11-16 14:13:52.238011089+01:00" level=warning msg="Forcing ctr_stop_timeout to lowest possible value of 30s"
# time="2020-11-16 14:13:52.238027582+01:00" level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_NET_RAW, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_SYS_CHROOT, CAP_KILL"
# time="2020-11-16 14:13:52.238353453+01:00" level=info msg="Using conmon executable: /home/vrubiolo/Documents/Dev/repos/community/crio-lxc/packages//conmon/bin/conmon"
# time="2020-11-16 14:13:52.239838784+01:00" level=info msg="Conmon does support the --sync option"
# time="2020-11-16 14:13:52.239864465+01:00" level=info msg="Using pinns executable: /home/vrubiolo/Documents/Dev/repos/community/crio-lxc/packages//cri-o/bin/pinns"
# time="2020-11-16 14:13:52.239877819+01:00" level=info msg="Seccomp is disabled by the system or at CRI-O build-time"
# time="2020-11-16 14:13:52.239885843+01:00" level=info msg="AppArmor is disabled by the system or at CRI-O build-time"
# time="2020-11-16 14:13:52.239929963+01:00" level=fatal msg="Validating runtime config: cgroupfs manager conmon cgroup should be 'pod' or empty"
# time="2020-11-16T14:13:54+01:00" level=fatal msg="failed to connect: failed to connect: context deadline exceeded"

Could sb shed light on the error? It is not obvious to me what the problem is (wrong cgroup name for conmon but I don't know why).

Here is the full log : make_check_log.txt

Git repo information for the packages : git_info.txt

This is Fedora 32.

Thanks much for your help and guidance !

@vrubiolo vrubiolo changed the title Unable to run 'make check' Unable to run 'make check' using master branch ("cgroupfs manager conmon cgroup should be 'pod' or empty") Nov 16, 2020
@vrubiolo vrubiolo changed the title Unable to run 'make check' using master branch ("cgroupfs manager conmon cgroup should be 'pod' or empty") make check' cannot run on master branch ("cgroupfs manager conmon cgroup should be 'pod' or empty") Nov 16, 2020
@vrubiolo
Copy link
Author

Hi there, are there any news on this issue?

@r10r
Copy link
Contributor

r10r commented Apr 21, 2021

This should not be an issue anymore with v0.11.0.

@r10r r10r closed this as completed Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants