Failed monitor with on-block=fail outside of resource group causes restart of resources inside of resource group?
Issue
We have a resource outside of resource group (outside_resource) that has monitor operation with on-fail=block behaviour and ordering constraint where this outside_resource depends on "non-last" resource in resource group (inside_resource_2). When the monitor operation on this outside_resource fails, then it will get blocked as expected, but the inside_resource_3 got also restarted.
outside_resource FAILED node1 (blocked)
Resource Group: grp
inside_resource_2 Started node2
inside_resource_3 Started node2 <---- was restarted when outside_resource 'monitor' failed
Ordering Constraints:
start inside_resource_2 then start outside_resource (kind:Mandatory)
Environment
- Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage Add-on
- having order constraint to make resource inside resource group start before resource outside resource group that uses
on-fail=blockonmonitoroperation
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
