Description of problem: As I understood running system roles is for most of the components only setting things up without verifying them. Running rhel-system-roles.ha_cluster seems to be different because it makes no sense for most thing to setting it up without cluster being running. My expectation would be that after running the role which ends green the cluster would be in a good state. Good state is when all the configure resources are in the desired (running?) state and the cluster is quorate. This is especially painful as the role takes long time to run. How reproducible: always Steps to Reproduce: 1. run the role with correct configuration that is "wrong" for example incorrect fencing ips Actual results: role finishing with green status but fencing not running Expected results: role finishing with green status only when cluster quorate and resources in desired (running?) state, red otherwise Additional info: This could be probably made optional to not break current workflow. It would probably useful to make resource/stonith/cluster quorate conditions separately selective.