Bug ID 1004605: Under rare conditions, blades may fail to start partition platform containers

Last Modified: Nov 22, 2021

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

Opened: Mar 22, 2021
Severity: 3-Major


After encountering a rare import bug, subsequent upgrades of partition software may result in a state where blades in a partition fail to start partition platform services after a system controller failover event.


Partition performance is degraded or disrupted.


1. A rare issue leads to the conditions of ID 984977 occurring during an import of some version of the partition ISO or services. 2. That version of partition services is configured for use by an active partition. 3. The system controllers fail over and switch active/standby roles. 4. Blades in partition are rebooted. 5. Blades fail to pull and start partition services, or pull and start the wrong version of services.


1. Remove all software configuration for the affected partition and disable the partition. 2. Re-enable the partition and re-configure the software versions you wish to use. or 1. In bash on the affected blade(s), run 'cp /var/export/chassis/partition/<partition ID>/blade/* /var/docker/config/' 2. Reboot the affected blade(s). Both workarounds will only persist until the next time the system controllers fail over, at which point they would need to be performed again. A more persistent workaround will require more involved, case-by-case modification of import structure by a support engineer.

Fix Information


Behavior Change