Hmm, I think the hostnames are wrong.

build21-b4, build22-b4, build23-b4, build72-b4 are swarming bots (and have been for over a year)
build21-b1, build22-b1, build23-b1, build72-b1 are currently unallocated android bots. I think these are the droids you're looking for.

+ charliea@ who submitted https://chromium-review.googlesource.com/c/445796/
I think we need to change the hostnames here?

I think I tried to restart that master? Maybe it didn't work?

See https://chrome-internal-review.googlesource.com/c/331250/ and https://bugs.chromium.org/p/chromium/issues/detail?id=696051

Re: #2. bpastene@ is correct.

If we were to follow our security model build21-b1, build22-b1, build23-b1, build72-b1 should be renamed as build*-b4 if they are connecting to master4a.

Are there any updates on this bug?

We need some labs help. The bots requested in bug 681066 are -b1, which means they can't connect to master4, which is where tryserver.chromium.perf lives, I think. Posting on the bug. 

Issue 696051 has been merged into this issue.

Reassigning to martiniss@, who's really leading the effort to get these online.

martiniss@, any idea what we should do now that pschmidt@ has renamed the bots to *-b4?

Need a CL to switch the bot names in slaves.cfg. Uploading one now.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/36e7f1be5ccbe2bfb7349373b41c4a6e962ef0bb

commit 36e7f1be5ccbe2bfb7349373b41c4a6e962ef0bb
Author: Stephen Martinis <martiniss@google.com>
Date: Thu Mar 02 21:34:28 2017

Bots are up and running tasks.

Thanks for fixing this Stephen! (Sorry, running behind on email.)