Bug ID 1296997: Large core files can cause system instability

Last Modified: Oct 21, 2024

Affected Product(s):
F5OS F5OS(all modules)

Known Affected Versions:
F5OS-A 1.1.0, F5OS-A 1.1.1, F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2, F5OS-A 1.4.0, F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.1

Fixed In:
F5OS-A 1.8.0, F5OS-A 1.5.2

Opened: May 09, 2023

Severity: 2-Critical

Symptoms

When a system generates and stores large core files, it can cause the system unstable.

Impact

F5OS core-writing script does not check filesystem availability before writing a core file and can fill up the filesystem, causing catastrophic system instability until disk-space is reclaimed. For more information of other impacts see 1185577 - F5OS-A memory leak in ImageAgent process on rSeries hosts may affect tenant performance or lead to unexpected restarts of tenant or host https://cdn.f5.com/product/bugtracker/ID1185577.html 1284705 - Appliance Orchestration Manager core file may consume entire root filesystem https://cdn.f5.com/product/bugtracker/ID1284705.html 1290949 - Invalid memory read in appliance orchestration manager https://cdn.f5.com/product/bugtracker/ID1290949.html 1327701 - Space in SNMP community/user/target name causing snmpd container restart https://cdn.f5.com/product/bugtracker/ID1327701.html

Conditions

F5OS generates a large core file.

Workaround

None

Fix Information

F5OS now takes into account the available filesystem space before writing a core file. If the core file is too large then it will be truncated and deleted to maintain system stability. The system log message will indicate if the core file was too large to safely write.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips