Last Modified: Sep 04, 2025
Affected Product(s):
F5OS F5OS-A, F5OS-C, Install/Upgrade, Velos
Known Affected Versions:
F5OS-A 1.8.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.8.0, F5OS-C 1.8.1
Opened: Apr 11, 2025 Severity: 3-Major
After a VELOS system controller, blade, or rSeries appliance has been running for several hundred days, the NetworkManager service may start leaking memory. This will eventually result in system instability including a failover between system controllers, or instability to tenants. Log messages similar to the following occurring in /var/log/messages or the systemd journal: controller-2.chassis.local NetworkManager[180091]: gsignal.c:2642: instance '0x564069a2be40' has no handler with id '34120' Prior to these log messages being generated, there is no way to tell how close to occurring the issue is.
NetworkManager service utilizes high memory in the system, which leads to controller failover.
The NetworkManager service has been running for a substantial period of time (i.e. more than 500 days).
Restart NetworkManager by logging in to the appropriate device as root (system controller, blade, or appliance) and running the command "systemctl restart NetworkManager".
None