Comment 6 for bug 1687095

In Eoan:

$ sudo crm cluster health
/usr/lib/python3/dist-packages/crmsh/scripts.py:431: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
  data = yaml.load(f)
INFO: Verify health and configuration
INFO: Nodes: cluster01, cluster02, cluster03
OK: Collect information
Ctrl-C, leavinglth check...

<hangs>

It looks like, despite parallax, crm cluster health might need *a real* fix in Eoan as well.

After the command is issued, it hangs and one of the nodes has:

root 14476 0.0 0.0 2864 2116 ? Ss 21:46 0:00 /bin/sh /usr/sbin/hb_report __slave DEST=health-report FROM_TIME=1567460760.0 TO_TIME=0 USER_NODES= NODES=cluster01 cluster02 cluster03 HA_LOG=/var/log/syslog SANITIZE=passw.* DO_SANITIZE=0 SKIP_LVL=False EXTRA_LOGS=/var/log/syslog /var/log/pacemaker/pacemaker.log /var/log/pacemaker.log /var/log/ha-cluster-bootstrap.log PCMK_LOG=/var/log/pacemaker/pacemaker.log /var/log/pacemaker.log VERBOSITY=0

And it is basically waiting on a read() - likely from "cat".

When issuing the hb_report by hand:

hb_report -n "cluster01 cluster02 cluster03" -f 10:00 -t 21:00

I'm able to get the report (important for a remote debug, for example).

For me, this is likely an issue in between crmsh <-> cluster-glue compatibility due changes in one or another over time.

I'll review this later as crmsh is in -universe and this is not one of its core functions to be cleaned up right now.