Bug ID 1289997: Tenant clustering fails when adding a lower number slot to Tenant

Last Modified: Mar 30, 2024

Affected Product(s):
BIG-IP Velos(all modules)

Known Affected Versions:
14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1, 15.1.10

Opened: Apr 18, 2023

Severity: 3-Major

Symptoms

If an existing Tenant is expanded to a new blade with a blade slot lower than any blade slot the Tenant is already running on, the Tenant can fail to cluster after a tenant reboot.

Impact

The Tenant can intermittently fail to cluster after a Tenant reboot.

Conditions

An existing Tenant is expanded to a new blade with a blade slot lower than any blade slot the Tenant is already running on.

Workaround

In the partition CLI, set the tenant to provisioned, then back to deployed.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips