Bug ID 992477: Tenant does not start up with the right config after frequent running-state changes

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
F5OS Velos(all modules)

Known Affected Versions:
1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2.0, 1.2.1, 1.2.2

Opened: Feb 11, 2021
Severity: 3-Major


If you create a tenant and set the running-state to deployed, (do not wait for full startup), immediately change the running-state to provisioned (do not wait for state change), immediately change tenant config such as vCPU/memory/VLANs/etc, and then immediately change back to deployed, the tenant starts up fine but may not come up with the right resources/config.


The tenant starts up with inaccurate resources (e.g., vCPU/memory/VLANs/mgmt-ip).


This occurs when the tenant running-state changes with no wait time in between state changes.


Wait a minimum of 30 seconds to 1 minute between when the tenant running-state transitions from one state to another. One way to ensure the clean transition is to verify the following state if the tenant is reached the desired state. -- If performing deployments from CLI: show tenants tenant <tenant-name> state status For example: If the tenant running-state is 'deployed': default-1# show tenants tenant defaultbip-1 state running-state state running-state deployed Verify the transition state if it reached the desired state: 'running' (if running-state set to deployed). default-1# show tenants tenant defaultbip-1 state status state status Running -- If performing deployments from the GUI, verify the tenant status next to the state under Tenant Management :: Tenant Deployments.

Fix Information


Behavior Change