Last Modified: Apr 28, 2025
Affected Product(s):
F5OS Velos
Fixed In:
F5OS-C 1.8.0
Opened: Dec 01, 2022 Severity: 2-Critical
If nodes are added to the tenant, then tenant management IP may bounce between nodes of a tenant instance. There may also be data plane issues where traffic will not be routed to the nodes added to an existing tenant instance. This occurs because the slot masks are not being updated in the existing tenant instances.
Data plane traffic may be impacted, and management access to the tenant IP may be unreliable.
- Nodes are added or removed from a BIG-IP tenant instance on F5OS.
- If the node population of a tenant has already been modified, then as a workaround configure the tenant to provisioned and then back to deployed. This will restart all the tenant instances and make the node masks consistent across all instances. If a node population change is planned, then the as a workaround configure the tenant to provisioned, configure the different node population on the tenant and then configure back to deployed.
Dynamic updates of the node population are allowed.