Bug ID 755585: mcpd can restart on secondary blades if a policy is created, published, and attached to a virtual server in a single transaction

Last Modified: Nov 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2

Fixed In:
15.0.0,, 13.1.3

Opened: Jan 15, 2019
Severity: 2-Critical


On a VIPRION cluster, if a single transaction creates a policy with the name Drafts/NAME, publishes the policy, and attaches the policy to a virtual server, mcpd restarts on the secondary blades.


mcpd restarts on all secondary blades of a cluster.


-- VIPRION chassis with more than one blade. -- Single mcp transaction that: * Creates a policy with 'Drafts/' as part of the policy name. * Publishes that policy. * Attaches that policy to a virtual server, either in the same transaction or a later transaction.


You can use either of the following workarounds: -- Do not create policies with 'Drafts/' in the name. -- Do not create and publish a policy in the same transaction.

Fix Information


Behavior Change