Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(CM) Install/Upgrade, TMOS
Known Affected Versions:
20.2.0, 20.2.1
Opened: Sep 17, 2024 Severity: 1-Blocking
The CM install process can be initiated by clicking the button in the GUI after logging in for the first time. CM install can also be done via CLI: /opt/cm-bundle/cm install After that the system may hang during the install. To verify this specific defect, check the end of the /var/log/central-manager/central-manager-cli.log file and it will end here: Release "kafka" does not exist. Installing it now. NAME: kafka LAST DEPLOYED: Sat Aug 3 11:02:57 2024 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None 2024-08-03T11:03:21+00:00 info: Installing central manager application resources... secret/cm-bootstrap-status patched Release "mbiq" does not exist. Installing it now.
Central Manager install never completes.
- New Central Manager deployment - "setup" has been run - The CM install process has been started via web UI or CLI
There are two options: 1. Delete the Central Manager instance and deploy a new one. 2. At the CLI, run uninstall and install again: # /opt/cm-bundle/cm uninstall Wait for this to complete, then: /opt/cm-bundle/cm install
None