Bug ID 1819873: Tenant may not come to Running state after quick movement of slots between partitions

Last Modified: Jun 26, 2025

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

Known Affected Versions:
F5OS-C 1.8.1

Opened: Feb 18, 2025

Severity: 2-Critical

Symptoms

After quick movement of a slot between different partitions, it is possible that tenants on that slot will not come back to the Running state.

Impact

Tenant may not come to Running state.

Conditions

This situation can occur if nodes are moved from current partition to another partition and then back to original partition.

Workaround

Toggle the running-state of the tenant from deployed to configured and then back to deployed.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips