Last Modified: Feb 26, 2019
See more info
Known Affected Versions:
13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.0, 22.214.171.124, 126.96.36.199
Opened: Jan 15, 2019
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.