Comment 3 for bug 1838556

This bug report deserves some history to help avoid confusion:

- multinode010 had the issue reported in this bug because the health check can't handle custom ceph cluster names

- PS3 of https://review.opendev.org/#/c/673545 succeeded on multinode010 if it doesn't use a custom ceph cluster name

- However, we want multinode010 to continue testing custom ceph cluster names so 673545 depended on https://review.opendev.org/#/c/674217 in ps4

- https://review.opendev.org/#/c/674217 then merged (but shouldn't have) and introduced the symptoms in this bug into voting scenarios 001/004

- 674217 was then reverted in https://review.opendev.org/#/c/674771 and voting scenarios 001/004 are green again

- We now just have non-voting multinode010 broken and its fix, 673545, will need to depend on an update to validations which supports custom cluster names but doesn't introduce problems the way that 674217 did.

Next things to do:

1. patch to tripleo-validations which Improve Ceph health checks to work with custom cluster names
2. revise patch 673545 to depends on 1