Bug ID 1967681: 17.1.2.2 OEM YK image does not fully boot as an F5OS tenant because mcpd does not start.

Last Modified: Jun 17, 2025

Affected Product(s):
BIG-IP F5OS-A, F5OS-C, Install/Upgrade, LTM, TMOS(all modules)

Known Affected Versions:
17.1.2.2

Opened: Jun 13, 2025

Severity: 2-Critical

Symptoms

BIGIP-OEM-YK-17.1.2.2-0.0.12.ALL-F5OS.qcow2.zip.bundle is missing critical files for F5OS tenant operation and does not fully boot.

Impact

The tenant does not fully boot. mcpd does not fully start with logs similar to the following in /var/log/ltm Jun 13 02:59:31 localhost.localdomain notice promptstatusd[7701]: 01460006:5: semaphore mcpd.running(1) held Jun 13 02:59:31 localhost.localdomain warning promptstatusd[7701]: 01460005:4: mcpd.running(1) held, wait for mcpd Jun 13 03:00:02 localhost.localdomain warning diskmonitor[8436]: 011d0002:4: Cannot access the database because mcpd is not running. [root@localhost:NO LICENSE:] config # bigstart status mcpd mcpd down, Waiting for chmand start: 42 seconds

Conditions

F5OS tenant BIGIP-OEM-YK-17.1.2.2-0.0.12.ALL-F5OS.qcow2.zip.bundle used to deploy the tenant.

Workaround

Use the 17.5.0 qcow image Use the 17.1.2.1 qcow image and upgrade to 17.1.2.2 using the .iso image.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips