View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017783 | CentOS-7 | kernel | public | 2020-10-07 13:39 | 2020-10-07 13:39 |
| Reporter | rswdc | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | random |
| Status | new | Resolution | open | ||
| Product Version | 7.8-2003 | ||||
| Summary | 0017783: Kernel/Cgroup memory allocation | ||||
| Description | Related to RH Case: 02759222 Here are links to the bug reports that we appear to be running in to; https://github.com/docker/for-linux/issues/841 https://bugzilla.redhat.com/show_bug.cgi?id=1507149 These pods are in an environment of Kubernetes on Openstack and produce errors similar to below; unable to ensure pod container exists: failed to create container for [kubepods besteffort podc884b870-3f95-40fb-bf75-9d605a1a6bf9] : mkdir /sys/fs/cgroup/memory/kubepods/besteffort/podc884b870-3f95-40fb-bf75-9d605a1a6bf9: cannot allocate memory unable to ensure pod container exists: failed to create container for [kubepods besteffort podd64e638f-c2d3-49e8-ac47-6fbd1db30b6d] : mkdir /sys/fs/cgroup/memory/kubepods/besteffort/podd64e638f-c2d3-49e8-ac47-6fbd1db30b6d: cannot allocate memory. --- I've attached the sosreport of the instance RH asked specifically to carry over; | ||||
| Steps To Reproduce | Unfortunately, as I understand, this is kind of happening at random... | ||||
| Additional Information | If more details are needed, please let us know. | ||||
| Tags | No tags attached. | ||||
| abrt_hash | |||||
| URL | |||||
| child of | 0017780 | new | Kernel/Cgroup memory allocation |
