Comment 3 for bug 1830421

Before reboot, both hypervisor were up.

[2019-05-24 15:05:52,384] 262 DEBUG MainThread ssh.send :: Send 'openstack --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://keystone.openstack.svc.cluster.local/v3 --os-user-domain-name Default --os-project-domain-name Default --os-identity-api-version 3 --os-interface internal --os-region-name RegionOne hypervisor list'
[2019-05-24 15:05:54,574] 387 DEBUG MainThread ssh.expect :: Output:
+----+---------------------+-----------------+---------------+-------+
| ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |
+----+---------------------+-----------------+---------------+-------+
| 3 | controller-0 | QEMU | 192.168.206.3 | up |
| 5 | controller-1 | QEMU | 192.168.206.4 | up |
+----+---------------------+-----------------+---------------+-------+

After reboot,
hypervisor list cmd not working due to another issue
https://bugs.launchpad.net/starlingx/+bug/1829931 - Standby controller not up in hypervisor list in 15 mins after host-unlock

There is another 270.001 alarm
| 270.001 | Host controller-1 compute services failure, failed to disable nova services
also pop up in alarm list sometimes, but it was cleared eventually.
Only alarm "270.001 Host controller-0 compute services failure, failed to get openstack token from keystone" stays in the list until the end of entire test suite