2

I have a Pacemaker setup with two STONITH resources. They have location constraints that crm configure show lists as follows:

location loc_stonith_node1 stonith_node1 rule -inf: #id eq node1
location loc_stonith_node2 stonith_node2 rule -inf: #id eq node2

Yet crm status indicates that both resources are started on node2:

stonith_node1   (stonith:external/ipmi):    Started node2
stonith_node2   (stonith:external/ipmi):    Started node2

This situation even persists if I crm resource stop and then crm resource start both resources. What could explain that the location constraints are apparently not obeyed?

UPDATE If I crm resource migrate stonith_node2 node1, the resource starts on node1, but if I then crm resource unmigrate stonith_node2 it immediately bounces back to node2.

rookie09
  • 673

1 Answers1

2

I've overcome the problem by switching to another syntactic form for the location contraints that requires neither references to #id nor #uname:

location loc_stonith_node1 stonith_node1 -inf: node1
location loc_stonith_node2 stonith_node2 -inf: node2
rookie09
  • 673