I believe this is blocking all CQ runs.  Pri=0.

I've removed the problem moblab instance from the CQ pool; there are
three other instances available, so that should be enough.

I've filed http://b2/28416715 for further action.

Also, I'm pretty sure that this shouldn't have caused CQ run
failures, so that needs a look-see all its own.

I just saw another failure 9 minutes ago:

https://uberchromegw.corp.google.com/i/chromeos/builders/guado_moblab-paladin/builds/2435

So we still have a problem.

Although, that build started right around when comment #4 was made. I would have guessed the lack of DUTs would be noticed later though (like, 80 minutes in, when the HWTests failed).

We've definitely removed the failing Moblab instance.
The recurrence likely means that the cause is a bad CL,
not a bad Moblab.

CQ keeps failing still https://uberchromegw.corp.google.com/i/chromeos/builders/guado_moblab-paladin/builds/2437 

Re #10: Yep, looks like chromeos2-row5-rack10-host9 is the culprit this time: "provision: FAIL: Moblab process: dhcpd is not running., completed successfully"

I updated b/28416715 to see if we can get that machine repaired.

The issue with guado_moblab-paladin seems fixed: https://uberchromegw.corp.google.com/i/chromeos/builders/guado_moblab-paladin

Closing. please reopen if its not fixed.