Bug ID 1003461: If the initial partition database startup is interrupted, it can leave an empty database

Last Modified: Jan 26, 2024

Affected Product(s):
F5OS Install/Upgrade, Velos(all modules)

Known Affected Versions:
F5OS-C 1.0.0, F5OS-C 1.1.0, F5OS-C 1.1.1

Fixed In:
F5OS-C 1.1.2

Opened: Mar 17, 2021

Severity: 2-Critical

Symptoms

After the partition initially starts up, the partition cannot be used because there are no users or roles defined.

Impact

The partition cannot be used, since it is not possible to log in and set a configuration.

Conditions

A problem occurs when the partition is starting up for the first time. This could happen if the partition were disabled shortly after being enabled, or if a controller failover occurs at the wrong time. The problem will not occur after the database has initialized correctly.

Workaround

After a partition is created, if it is not possible to log in, the chassis administrator can remove all slots from the partition and delete it. After the transaction commits, re-create the partition with the desired slots.

Fix Information

The database software correctly detects and recovers from this condition.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips