Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
ERROR: 23270 -- container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"write /sys/fs/cgroup/pids/system.slice/docker-ed3fa4e82fe8fd0837bdb958cf7a5421708dc45404dd4b52f45875f0d3136f53.scope/cgroup.procs: no such device\\\"\"",
"/usr/bin/docker-current: Error response from daemon: invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:258: applying cgroup configuration for process caused \\\\\\\"write /sys/fs/cgroup/pids/system.slice/docker-ed3fa4e82fe8fd0837bdb958cf7a5421708dc45404dd4b52f45875f0d3136f53.scope/cgroup.procs: no such device\\\\\\\"\\\"\\n\".",
Version-Release number of selected component (if applicable):
docker-1.12.6-68.gitec8512b
How reproducible:
No easy reproducer known.
I got the issue at osp12 installation time.
Additional info:
docker-1.12.6-68.gitec8512b.el7.src.rpm is using the runc-c5d311627d39439c5b1cc35c67a51c9c6ccda648 where the communication with systemd is not synchronized.
Related changes:
https://github.com/openshift/origin/pull/18106/commits/6d2d90f108384ec3b3736401d121895c8936da1dhttps://github.com/containerd/cgroups/commit/688877e020ff76554d29097c856724220e9f3689#diff-af1b0554e367b884d60f6269dfffc476
According to https://github.com/openshift/origin/issues/16246 the above
change was fixed a similar issue at similar code location in a similar code base ;-)
Description of problem: ERROR: 23270 -- container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"write /sys/fs/cgroup/pids/system.slice/docker-ed3fa4e82fe8fd0837bdb958cf7a5421708dc45404dd4b52f45875f0d3136f53.scope/cgroup.procs: no such device\\\"\"", "/usr/bin/docker-current: Error response from daemon: invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:258: applying cgroup configuration for process caused \\\\\\\"write /sys/fs/cgroup/pids/system.slice/docker-ed3fa4e82fe8fd0837bdb958cf7a5421708dc45404dd4b52f45875f0d3136f53.scope/cgroup.procs: no such device\\\\\\\"\\\"\\n\".", Version-Release number of selected component (if applicable): docker-1.12.6-68.gitec8512b How reproducible: No easy reproducer known. I got the issue at osp12 installation time. Additional info: docker-1.12.6-68.gitec8512b.el7.src.rpm is using the runc-c5d311627d39439c5b1cc35c67a51c9c6ccda648 where the communication with systemd is not synchronized. Related changes: https://github.com/openshift/origin/pull/18106/commits/6d2d90f108384ec3b3736401d121895c8936da1d https://github.com/containerd/cgroups/commit/688877e020ff76554d29097c856724220e9f3689#diff-af1b0554e367b884d60f6269dfffc476 According to https://github.com/openshift/origin/issues/16246 the above change was fixed a similar issue at similar code location in a similar code base ;-)