Back to bug 1987041
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2021-07-28 19:11:47 UTC | Link ID | Red Hat Issue Tracker RHCEPH-638 | |
| Vikhyat Umrao | 2021-07-29 17:46:02 UTC | CC | vumrao | |
| Dimitri Savineau | 2021-07-30 17:53:14 UTC | Status | NEW | ASSIGNED |
| Target Release | 5.1 | 4.3 | ||
| CC | dsavinea | |||
| Link ID | Github ceph/ceph-ansible/pull/6777 | |||
| Assignee | gabrioux | tonay | ||
| Red Hat One Jira (issues.redhat.com) | 2021-07-30 17:57:49 UTC | Link ID | Red Hat Issue Tracker RHCEPH-638 | |
| Veera Raghava Reddy | 2021-08-02 01:46:59 UTC | CC | vereddy | |
| Dimitri Savineau | 2021-08-05 14:01:06 UTC | Link ID | Github ceph/ceph-ansible/pull/6789 | |
| Status | ASSIGNED | POST | ||
| Giulio Fidente | 2021-08-10 16:07:56 UTC | Blocks | 1760354 | |
| CC | gfidente | |||
| Matthias Muench | 2021-08-16 16:05:49 UTC | CC | mmuench | |
| errata-xmlrpc | 2021-08-18 19:42:20 UTC | Status | POST | MODIFIED |
| Fixed In Version | ceph-ansible-4.0.64-1.el8cp, ceph-ansible-4.0.64-1.el7cp | |||
| CC | tserlin | |||
| Status | MODIFIED | ON_QA | ||
| Red Hat One Jira (issues.redhat.com) | 2021-08-18 21:58:46 UTC | Link ID | Red Hat Issue Tracker RHCEPH-638 | |
| Sunil Kumar Nagaraju | 2021-09-14 16:51:00 UTC | CC | sunnagar | |
| Sunil Kumar Nagaraju | 2021-09-15 07:16:52 UTC | Status | ON_QA | VERIFIED |
| Sunil Kumar Nagaraju | 2021-09-15 07:18:00 UTC | QA Contact | amsyedha | sunnagar |
| Ranjini M N | 2021-11-12 07:55:30 UTC | CC | rmandyam | |
| Flags | needinfo?(tonay) | |||
| Teoman ONAY | 2021-11-22 08:48:34 UTC | Flags | needinfo?(tonay) | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Doc Text | Cause: Default values of pid-limits for podman (2048) and docker (4096) might be insufficient when the user customizes some values like http-threads close to these limits Consequence: The container fails to start as the number of processes it needs to start is higher than the allowed limit. Fix: remove that limit of maximum processes that can be started within a container by adding the --pid-limits parameter (-1 for podman & 0 for docker) to the systemd service file Result: Containers will start even if the user customize some internal processes which might require to run more processes than the default limits. |
|||
| Ranjini M N | 2021-12-22 10:09:26 UTC | Flags | needinfo?(tonay) | |
| Doc Text | Cause: Default values of pid-limits for podman (2048) and docker (4096) might be insufficient when the user customizes some values like http-threads close to these limits Consequence: The container fails to start as the number of processes it needs to start is higher than the allowed limit. Fix: remove that limit of maximum processes that can be started within a container by adding the --pid-limits parameter (-1 for podman & 0 for docker) to the systemd service file Result: Containers will start even if the user customize some internal processes which might require to run more processes than the default limits. | .The systemd service file now supports the `--pid-limits` parameter to customize internal process limits Previously, when the default value of the pid-limits was changed from the default value of 2048 for podman and 4096 for the docker, the container failed to start as the number of processes it needed to start was higher than the allowed limit. With this release, you can remove the limit of maximum processes that can be started by adding the `--pid-limits` parameter as `-1` for podman and as `0` for docker to the systemd service file. As a result, the containers start even if you customize the internal processes which might need to run more processes than the default limits. |
||
| Ranjini M N | 2021-12-22 11:39:01 UTC | Blocks | 2031070 | |
| Teoman ONAY | 2021-12-22 13:27:35 UTC | Flags | needinfo?(tonay) | |
| Ranjini M N | 2021-12-24 13:23:36 UTC | Doc Text | .The systemd service file now supports the `--pid-limits` parameter to customize internal process limits Previously, when the default value of the pid-limits was changed from the default value of 2048 for podman and 4096 for the docker, the container failed to start as the number of processes it needed to start was higher than the allowed limit. With this release, you can remove the limit of maximum processes that can be started by adding the `--pid-limits` parameter as `-1` for podman and as `0` for docker to the systemd service file. As a result, the containers start even if you customize the internal processes which might need to run more processes than the default limits. | .Add the `--pid-limits` parameter as `-1` for podman and `0` for docker in the systemd file to start the container Previously, the number of processes allowed to run in containers, 2048 for podman and 4096 for docker, were not sufficient to start some containers which needed to start more processes than these limits. With this release, you can remove the limit of maximum processes that can be started by adding the `--pid-limits` parameter as `-1` for podman and as `0` for docker in the systemd unit files. As a result, the containers start even if you customize the internal processes which might need to run more processes than the default limits. |
| Victoria Martinez de la Cruz | 2022-01-06 09:51:25 UTC | Blocks | 1987235 | |
| Ranjini M N | 2022-01-13 06:45:01 UTC | Docs Contact | rmandyam | |
| errata-xmlrpc | 2022-05-05 06:07:56 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-05-05 07:53:24 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-05-05 07:53:24 UTC | |||
| errata-xmlrpc | 2022-05-05 07:53:51 UTC | Link ID | Red Hat Product Errata RHSA-2022:1716 |
Back to bug 1987041