Last Modified: Jun 26, 2025
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.6.2, F5OS-C 1.8.0
Fixed In:
F5OS-C 1.8.1
Opened: Oct 28, 2024 Severity: 3-Major
In rare cases the partition configuration volume can be wiped during a system controller reboot when partitions are disabled, resulting in partition configuration loss.
Partition and tenant configuration is lost, and must be restored from backup before continuing.
When partitions are disabled and a system controller is rebooted there can be a shutdown race between a (spurious) resize request and LVM shutdown that can cause one of the partition volumes to get removed. When the partition is subsequently enabled, whichever controller instance starts first will establish the current configuration. If the instance that was removed starts first, the partition is reinitialized to a clean configuration. If the partition is running when the system controller reboots it will automatically resync itself from the other system controller as soon as it restarts. Configuration loss is not observed, though there may be missing logfiles on one of the system controller partition instances.
Partitions should be left enabled. As long as at least one partition instance is running, the high availability subsystem will ensure that no configuration is lost. Chassis power loss won't trigger this problem since there won't be a "race" between the stopping components.
The spurious resizes no longer occur, and the error paths in partition volume resize and partition enablement can no longer result in removing the volumes.