Comment 2 for bug 1602749

This is reproducible still with Juju 2.5.1 and maas provider with maas 2.5.0-7442-gdf68e30a5-0ubuntu1~18.04.1.

I simulated a dead Juju controller machine by suspending a MAAS Pod VM responsible for one of the controller, but Juju reports all controller nodes are healthy.

$ virsh suspend juju-1 ## simulate an unresponsive controller

$ juju ssh -m controller 0 ## 0 = juju-1
ERROR cannot connect to any address: [192.168.151.22:22 192.168.151.22:22]

$ juju status -m controller; juju show-controller | grep ha-status:

Model Controller Cloud/Region Version SLA Timestamp
controller foundations-maas foundations-maas 2.5.1 unsupported 18:39:21Z

Machine State DNS Inst id Series AZ Message
0 started 192.168.151.22 cg6qmw bionic zone1 Deployed
1 started 192.168.153.22 4skcpe bionic zone3 Deployed
2 started 192.168.152.21 wshrgx bionic zone2 Deployed

      ha-status: ha-enabled
      ha-status: ha-enabled
      ha-status: ha-enabled

-> status doesn't report any down / unhealthy controller node even after 5 minutes.