Bug ID 1077105: Chassis Partition/Tenant pods might not start

Last Modified: May 17, 2022

Bug Tracker

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

Known Affected Versions:
1.3.0, 1.3.1

Fixed In:
1.3.2

Opened: Jan 31, 2022
Severity: 1-Blocking

Symptoms

Chassis Partition/Tenant pods might fail to start if the partition namespace key is missing or stale.

Impact

Chassis Partition/Tenant pods fail to start on a partition in this condition.

Conditions

Upgrading to F5OS-C v1.3.1 and creating a new partition, or deleting and creating an existing partition, either which is active on the Standby VELOS system controller.

Workaround

Fail over the active VELOS system controller, which causes the standby controller to generate the correct partition keys. To do this, from the command line on the active system controller type: "system redundancy go-standby"

Fix Information

This issue is fixed.

Behavior Change