Bug ID 2293577: On a vCMP Host VIPRION Chassis, Running vCMP Guests May Adopt An Incorrect Identity Following Simultaneous MCPD Restarts On Multiple Blades

Last Modified: Jun 15, 2026

Affected Product(s):
BIG-IP vCMP(all modules)

Known Affected Versions:
17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6

Opened: May 06, 2026

Severity: 3-Major

Symptoms

- A guest answers on the management IP address of a different guest - A guest presents the hostname, unit key, or SSL credentials of a different guest - Processes inside the affected guest log master key decryption failures similar to the following in /var/log/audit: 01071769:3: Decryption of the field (admin_password) for object (/Common/<object_name>) failed while loading the configuration that is encrypted with a different master key.

Impact

The guests become unreachable.

Conditions

All of the following conditions must be met: - The VIPRION system is provisioned as a vCMP host with two or more deployed guests spanning multiple blades - mcpd restarts simultaneously on multiple blades - vcmpd reattaches to the still-running guest QEMU processes following the restart

Workaround

Redeploy the guests. tmsh modify vcmp guest <name> state configured tmsh modify vcmp guest <name> state deployed

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips