Why I see fencing of nodes and Failed actions in cluster with multiple `IPsrcaddr` resources?

Solution Unverified - Updated -

Issue

  • When multiple IPsrcaddr resources are running in cluster on different nodes the following messages are observed in pcs status output. How can I remove these messages?

    ipsrcaddr1_monitor_0 on node2 'unknown error' (1): call=93, status=complete, exitreason='none', last-rc-change='Wed Sep  6 14:18:33 2017', queued=0ms, exec=36ms
ipsrcaddr2_monitor_0 on node1 'unknown error' (1): call=103, status=complete, exitreason='none', last-rc-change='Wed Sep  6 14:18:35 2017', queued=0ms, exec=50ms

  • When two IPsrcaddr resources are started on one cluster node, cluster is fencing this node. How to prevent this?

Environment

  • Red Hat Enterprise Linux 6, 7 with High-Availability or Resilient Storage Add-on

  • Multiple IPsrcaddr resources are configured in cluster

     ipsrcaddr1     (ocf::heartbeat:IPsrcaddr):     Started node1
 ipsrcaddr2     (ocf::heartbeat:IPsrcaddr):     Started node2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content