Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) Install/Upgrade, TMOS
Known Affected Versions:
20.0.1, 20.0.2, 20.1.0, 20.1.1, 20.2.0, 20.2.1
Opened: Jun 10, 2024 Severity: 1-Blocking
During a CM upgrade, if the upgrade fails (for example, in an air-gap environment where the CM is disconnected from the internet), the version displayed in the GUI is different from the version shown in the CLI. Typically, the GUI retains the current version, while the CLI shows the target version that failed to upgrade. This discrepancy in version causes confusion about whether the upgrade was successful or not.
CM becomes dysfunctional, the failed upgrade leads to discrepancies in version representation, where the CM GUI displays the current version while the CLI indicates the target version.
Upgrade CM in an air-gapped environment.
If upgrade has failed due to a ephemeral condition(ie, pod startup timeout), user should restore CM to a previous version backup and retry upgrade to version of 20.2.1. Refer How to: Back up and restore BIG-IP Next Central Manager (https://clouddocs.f5.com/bigip-next/20-2-0/use_cm/cm_backup_restore_using_ui_api.html). if upgrading from 20.0.2->20.2.0 caused the failure and there is no backup, perform the following steps on your CLI to create a backup and restore back to 20.0.2: helm rollback mbiq-vault 1 (will fail) helm rollback mbiq-vault 1 (succeeds) kubectl get statefulset mbiq-vault -o yaml > vault.yaml vi vault.yaml #delete the line that reads "value: https://$(HOSTNAME).mbiq-vault-internal.default.svc.cluster.local:8200" kubectl delete statefulset mbiq-vault kubectl apply -f vault.yaml #wait for vault to come back up /opt/cm-bundle/cm backup #create new 20.0.2 CM #scp backup file to CM #restore using backup
None