Bug ID 1182569: After failed partial F5OS upgrade, system-manager will not start

Last Modified: Apr 28, 2025

Affected Product(s):
F5OS F5OS, Install/Upgrade(all modules)

Known Affected Versions:
F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2

Fixed In:
F5OS-A 1.4.0

Opened: Oct 20, 2022

Severity: 3-Major

Symptoms

The primary system management daemon docker container (system_manager) is not running. "docker logs system_manager" or the systemd journal or /var/log/message contains an error similar to the following: "Bad configuration: cdb/confd.conf:677: Element snmpEngineID is invalid: \"80:00:2f:f4:03:Invalid\" is not a valid value.\n"

Impact

The system remains inoperative.

Conditions

The F5OS-A services are upgraded to F5OS-A 1.2.0 while the OS remains at an earlier version. This might occur as a result of ID1181929: https://cdn.f5.com/product/bugtracker/ID1181929.html

Workaround

After the system F5OS OS and service versions match, remove /var/F5/system/cdb/engine-id and then reboot.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips