on our HyperFlex 4.0 clusters, the "Cluster Services Check" always fails in environments, where no replication is used.
the check runs "service_status.sh" and parses the output for certain service names. one of them is "Cluster IP Monitor".
this one will always fail in our environment, because there's another service called "Replication Cluster IP Monitor", which is not running because we don't have replication.
lines 580,581:
elif "Cluster IP Monitor" in line and "Not" in line:
cluster_service_chk = "FAIL"
on our HyperFlex 4.0 clusters, the "Cluster Services Check" always fails in environments, where no replication is used.
the check runs "service_status.sh" and parses the output for certain service names. one of them is "Cluster IP Monitor". this one will always fail in our environment, because there's another service called "Replication Cluster IP Monitor", which is not running because we don't have replication.
lines 580,581: elif "Cluster IP Monitor" in line and "Not" in line: cluster_service_chk = "FAIL"