The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/18346caa5f4f96f1286c96c44ca0ea36ebb39529

commit 18346caa5f4f96f1286c96c44ca0ea36ebb39529
Author: Richard Barnette <jrbarnette@google.com>
Date: Fri Aug 25 21:33:27 2017

... aaand there's another bug:

In the upstart job, there's this line:
    IPADDR=$(host $(hostname) | awk '{print $NF}')

That fails because of something in the local DNS config
(leastways, it fails on chromeos4-devserver7):
    chromeos-test@chromeos4-devserver7:~$ host $(hostname)
    chromeos4-devserver7.cros.corp.google.com has address 100.115.219.135
    Host chromeos4-devserver7.cros.corp.google.com not found: 3(NXDOMAIN)

Don't know what _that's_ all about, but it will have to be worked around.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/39f552dd2adb5cd4fe142b2ed557a78cefaef6e0

commit 39f552dd2adb5cd4fe142b2ed557a78cefaef6e0
Author: Richard Barnette <jrbarnette@google.com>
Date: Mon Aug 28 23:06:18 2017

$ for s in ${DEVSERVERS[@]}; do echo $s: $(ssh $s status provision-workqueue); done
100.107.126.136: provision-workqueue start/running, process 11402
100.107.126.137: provision-workqueue start/running, process 2696
100.107.126.159: provision-workqueue start/running, process 30051
100.107.126.160: provision-workqueue start/running, process 17078
100.107.126.161: provision-workqueue stop/waiting
100.107.126.163: provision-workqueue start/running, process 27137
100.107.126.164: provision-workqueue start/running, process 26022
100.107.126.165: provision-workqueue start/running, process 31286
100.107.126.174: provision-workqueue start/running, process 6249
100.107.126.175: provision-workqueue start/running, process 2080
100.107.156.241: provision-workqueue start/running, process 6623
100.107.156.243: provision-workqueue start/running, process 28595
100.115.24.253: provision-workqueue start/running, process 198897
100.115.93.188: provision-workqueue start/running, process 32500
100.115.99.236: provision-workqueue start/running, process 26281
100.115.99.246: provision-workqueue start/running, process 27530
100.115.99.247: provision-workqueue start/running, process 21679
100.115.99.251: provision-workqueue start/running, process 26765
100.115.99.252: provision-workqueue start/running, process 26040
100.115.185.226: provision-workqueue start/running, process 22205
100.115.185.227: provision-workqueue start/running, process 14163
100.115.185.228: provision-workqueue start/running, process 26819
100.115.219.129: provision-workqueue start/running, process 3388
100.115.219.130: provision-workqueue start/running, process 21292
100.115.219.132: provision-workqueue start/running, process 13914
100.115.219.133: provision-workqueue start/running, process 833
100.115.219.134: provision-workqueue start/running, process 12067
100.115.219.135: provision-workqueue start/running, process 20105
100.115.219.136: provision-workqueue start/running, process 612
100.115.219.139: provision-workqueue start/running, process 92136
100.115.245.197: provision-workqueue start/running, process 10898
100.115.245.198: provision-workqueue start/running, process 18919
100.115.245.200: provision-workqueue start/running, process 11298
100.120.7.235: provision-workqueue start/running, process 21297
100.120.7.236: provision-workqueue start/running, process 4766

I'm investigating 100.107.126.161, but the problem isn't the upstart
job.