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

Last Modified: Feb 26, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2

Opened: Jan 15, 2019
Severity: 2-Critical

Symptoms

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.

Impact

mcpd restarts on all secondary blades of a cluster.

Conditions

-- 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.

Workaround

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

None

Behavior Change