Last Modified: Jul 20, 2026
Affected Product(s):
F5OS F5OS-C
Fixed In:
F5OS v2.0.0
Opened: Dec 29, 2025 Severity: 3-Major
- A tenant is showing as deployed, has no running pods. - A tenant that is supposed to be running is not running while a deleted tenant is trying to come up (in terms of pods in the system).
Tenants may not reflect the latest committed configuration state.
Sequence of failover operations on the partition when tenant configuration changes were being processed
Failover the partition or recreate the tenant.
Updated standby cache regularly and cleared the stale info before orchestration daemon becomes the active one.