systemd excessively reads mountinfo and udev in dense container environments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Li Zhou |
Bug Description
Brief Description
-----------------
When testing a large number of pods (> 230), occasionally observed a number of issues related to systemd process:
systemd ran continually 90-100% cpu usage
systemd memory usage started increasing rapidly (20GB/hour)
systemctl commands would always timeout (Failed to get properties: Connection timed out)
sm services fail and can't recover: open-ldap, registry-
new pods can't start, get stuck in state ContainerCreating
This is verified to be a known issue:
https:/
Severity
--------
Major
Steps to Reproduce
------------------
Refer to [https:/
Expected Behavior
------------------
All of the pods are deployed successfully.
Actual Behavior
----------------
systemd ran continually 90-100% cpu usage
systemd memory usage started increasing rapidly (20GB/hour)
systemctl commands would always timeout (Failed to get properties: Connection timed out)
sm services fail and can't recover: open-ldap, registry-
new pods can't start, get stuck in state ContainerCreating
Reproducibility
---------------
Intermittent
System Configuration
-------
One node system
Test Activity
-------------
Developer Testing
Workaround
----------
None
CVE References
Changed in starlingx: | |
assignee: | nobody → Li Zhou (lzhou2) |
summary: |
- systemd excessively reads mountinfo and udev in dense OpenShift + systemd excessively reads mountinfo and udev in dense container environments |
Fix proposed to branch: master /review. opendev. org/c/starlingx /integ/ +/786599
Review: https:/