Balanced. Only the chromeos2-row8-rack8-host19  is replaced. chromeos2-row8-rack8-host9 is in Ready state, so it won't be removed from bvt pool by the script. I will take a look at the DUT tomorrow to see whether it needs a manual swap

A bit more data:

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/595
Suite fails because:
- Job: wizpig-release/R57-9010.0.0/bvt-inline/security_ChromiumOSLSM (86731395-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host9

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/594
Suite fails because:
- Job: wizpig-release/R57-9009.0.0/bvt-inline/security_ASLR (86625930-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host9
- Job: wizpig-release/R57-9009.0.0/bvt-inline/security_ASLR (86678915-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host14 (not sure what that's about, but appears to be a retry of the above)

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/593
Suite fails because:
- Job: wizpig-release/R57-9008.0.0/bvt-inline/login_OwnershipRetaken (86578628-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host9

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/591
Suite fails because:
- Job: wizpig-release/R57-9007.0.0/bvt-inline/provision_AutoUpdate.double (86537288-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host9
- Job: wizpig-release/R57-9007.0.0/bvt-inline/provision_AutoUpdate.double (86565373-chromeos-test)
  Scheduled to run on chromeos2-row8-rack6-host6 (retry?)

https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/590
Suite fails because:
- Job: wizpig-release/R57-9005.0.0/bvt-inline/login_OwnershipRetaken (86416368-chromeos-test)
  Scheduled to run on chromeos2-row8-rack8-host9

I think the pattern is quite clear, maybe rebalancing won't help if anything still gets scheduled on chromeos2-row8-rack8-host9.

Maybe we should lock chromeos2-row8-rack8-host9 for the time being?

Yeah, please lock it tonight to avoid more failures caused by this DUT.

Locked: http://cautotest.corp.google.com/afe/#tab_id=view_host&object_id=5973 .

Looks good now, wizpig-release turned green:
https://uberchromegw.corp.google.com/i/chromeos/builders/wizpig-release/builds/599

We should investigate what is wrong with chromeos2-row8-rack8-host9, though.

Pass to deputy