Last Modified: Sep 19, 2025
Affected Product(s):
F5OS F5OS-C, Velos
Known Affected Versions:
F5OS-C 1.8.1
Opened: Aug 29, 2025 Severity: 2-Critical
When performing a "system aaa primary-key set" operation, sometimes the controller will fail over prior to updating the database values, resulting in an inconsistent decryption key. The set key operation remains in 'IN_PROGRESS' and does not recover.
Configuration database will not be usable, partitions will not start correctly. System must be restored from backup.
Retry timing problem in the key retrieval logic sometimes causes the database to hang for over 30 seconds during configuration reload, resulting in the hardware watchdog expiring and causing a failover.
Prior to attempting to change the primary-key, ensure that a controller, partition, and tenant backups with a known primary-key are available. If the problem occurs, perform a "system database reset-to-default", reset the primary key to the previous known value corresponding to the backup and restore the backups.
None