Bug ID 1351249: Before deployments, if cpu_users database file has stale data then tenant deployment fails.

Last Modified: Oct 19, 2025

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

Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2

Opened: Sep 12, 2023

Severity: 3-Major

Symptoms

When tenant fails to reach deployed state. ConfD command "show tenants" may report not enough cpus.

Impact

A tenant may fail to come up, even when it appears the node's cpu limit has not been exceeded.

Conditions

There was some prior population of tenants on a blade. The blade is not powered up when a tenant is deleted in confD. This may result in stale data on the blade not getting cleaned up.

Workaround

Toggle all tenants on the affected blade to either the "provisioned" or "configured" state. 1. ssh to the blade. 2. rm /opt/f5/cpumgr/cpu_users 3. killall -9 virt-handler After this, toggle the desired tenants back to "deployed".

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips