Oyvind Albrigtsen

It should. So seems like we need to update it ro use -N/-R or combination of them to work optimally in this case: https://access.redhat.com/discussions/5474551

If you run `grep -e "run_command" -e "pexpect" agents/*/*.py` you should get most of the agents that might have similar issues if the tool they use uses internal timeout.

You have to run `./autogen.sh && ./configure` to generate it.

In fence_eps it's only when verbose logging is enabled (and also it's base64 encoded, so not in clear text either). fence_skalar also only does it with --verbose.

The monitor action should only report if it cant connect to fence_virtd or similar errors (so Pacemaker can show running, failed, etc). If you want the status of a VM...

fence_scsi is meant to disconnect access to shared storage, so e.g. your database or other resource(s) arent able to write to it when the node fails. To reboot the node...

Do you have a link to the sbd agent? I think it's Suse specific, so I dont know where to find it's source.

Thank you for the report. I'll look into how we should implement this.

I've added default permissions and checks in fence_virtd: https://github.com/ClusterLabs/fence-agents/pull/513

The agent doesnt currently support proxies.