The devserver I pushed to: chromeos6-devserver4

I've manually reverted chromeos6-devserver4's repos to be the same as chromeos6-devserver2
The service is back.

That devserver had a downtime of ~23 minutes.
+FYI: nxia.

Verified that I can stage a cros image on the devserver again.

Here's the monarch view of the badness this caused: http://shortn/_9RhBLy1uYg

 Issue 756581  has been merged into this issue.

looks like this devserver affects https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-paladin/builds/29312

In theory, it's safe to push to the devservers again.

In practice, we might wait for this CL:
    https://chromium-review.googlesource.com/#/c/chromiumos/platform/dev-util/+/621780/

I'm jittery about this push after my failed attempt on Friday.
We don't yet have a staging devserver story, and the deputies have their hands full this week.

I think the onus of proving that this push is safe falls back on jrbarnette@ in this case -- please push manually to one of the two staging devservers. Once test_push passes with your new code on the devservers, deputies will be willing to push this to prod.

+shuqianz@ can tell you which devservers are used for staging, and how to update them.

I've successfully updated chromeos2-devservertest, and seen
that the devserver restarted with ToT.

I also ran a simple sanity test against workqueue_server, to
confirm it can start and serve local (debug) requests.

Once we've seen what happens with the next test push to prod, we
should have enough data on whether it's safe to push to the main
lab.

The test push failed due to issues unrelated to the devserver.  There
was a successful provisioning task here:
    https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos2-row1-rack2-host1/25330-provision/debug/

I believe we should declare victory and push.

The push is done.  There are more pushes to come; those will be
separate bugs.