Bug ID 1593613: When an upgrade fails, CM cannot be restored and becomes dysfunctional due to multiple containers entering the 'CrashLoopBackOff' state

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(CM) Install/Upgrade, TMOS(all modules)

Known Affected Versions:
20.0.1, 20.0.2, 20.1.0, 20.1.1, 20.2.0, 20.2.1

Opened: Jun 11, 2024

Severity: 2-Critical

Symptoms

Upgrade from BIG-IP Next version 20.0.2 to version 20.2.0 fails with status of CrashLoopBackOff on several pods.

Impact

Central Manager is unusable due to pods not being in valid state.

Conditions

Upgrading from BIG-IP Next version 20.0.2 to version 20.2.0

Workaround

Restore CM to a previous version backup and upgrade to next minor version of 20.1.0. Refer How to: Back up and restore BIG-IP Next Central Manager (https://clouddocs.f5.com/bigip-next/20-0-2/use_cm/cm_backup-restore.html).

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips