Currently, the pool appears to be healthy. Perhaps this issue was transient or was fixed by an automated balance_pool run.

dut-status -b hana -p cq
hostname                       S   last checked         URL
chromeos6-row4-rack2-host3     OK  2018-10-17 08:06:09  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack2-host3/2047696-provision/
chromeos6-row4-rack2-host5     OK  2018-10-17 08:06:11  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack2-host5/2047700-provision/
chromeos6-row4-rack2-host13    OK  2018-10-17 08:06:11  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack2-host13/2047699-provision/
chromeos6-row4-rack2-host19    OK  2018-10-17 08:06:05  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack2-host19/2047695-provision/
chromeos6-row4-rack3-host1     OK  2018-10-17 08:06:11  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack3-host1/2047701-provision/
chromeos6-row4-rack3-host19    OK  2018-10-17 08:06:09  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack3-host19/2047697-provision/
chromeos6-row4-rack3-host13    OK  2018-10-17 08:06:09  https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos6-row4-rack3-host13/2047698-provision/