Bug ID 1084153: Tenant deployment will fail when we move tenant (deployed with max vCPU) from provisioned to deployed

Last Modified: Apr 28, 2025

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

Fixed In:
F5OS-A 1.4.0

Opened: Mar 01, 2022

Severity: 3-Major

Symptoms

Tenant deployment will fail when moved (deployed with max vCPU) from provisioned to deployed while the old resources are still terminating in the system.

Impact

Tenant deployment will be stuck in a pending state forever.

Conditions

When the same tenant is redeployed immediately, the appliance cannot allocate resources as the old resources were not released to the system yet. This issue is observed only on r2k/r4k but not on r5k/r10k.

Workaround

Move the tenant to provisioned state and wait for the tenant resources to terminate completely in the system and then move it to a deployed state.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips