I got the slave up and connected to the master but there is still a master configuration issue. 
  https://build.chromium.org/p/chromium.memory/builders/Linux%20TSan%20Builder/builds/0/steps/generate_build_files/logs/stdio

Issue 677159 has been merged into this issue.

CC'ing the current trooper.

don't see cc troopers, please; Infra-Troopers is sufficient. EMEA troopers don't handle Pri2 issues.

I think this bug should be closed in favor   https://crbug.com/672860#c16 . This is a VM and can be easily restarted by any infra person through https://chrome-infra.appspot.com/login?r=%2Fvm-power

This bug was filed in response to the suggestion in  https://crbug.com/672860#c17 , which was itself a response to  https://crbug.com/672860#c16 .

There's a priority mismatch here IMO given that this bug is causing an alert in sheriff-o-matic and causing a bot to be consistently red on the main waterfall.

Agree with #7 and bumping up to P1.

Fixing up labels so that a trooper can take a look.

Taking a look

I just restarted the VM. Let's see if that fixes things.

That doesn't seem to have helped. Taking another look.

Actually, I made a mistake. The master is restarting in fifteen minutes. 

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

commit 39f73e8d9470cb0732bf073250156ad5921c70ca
Author: Katie Thomas <katthomas@google.com>
Date: Wed Jan 04 19:13:24 2017

The error I see is:

MBErr: Builder name "Linux TSan Builder"  not found under masters[chromium.memory] in "/b/c/b/Linux_TSan_Builder/src/tools/mb/mb_config.pyl"

It is indeed not there...https://codesearch.chromium.org/chromium/src/tools/mb/mb_config.pyl?l=309

It also looks like it has never been successful: http://shortn/_HcoAT02PT2

I see this change: https://chromium.googlesource.com/chromium/tools/build/+/a4dc1bd4c41dd72b2fa83bed1047db1072b30554%5E%21/masters/master.chromium.memory/slaves.cfg

Maybe something was missing? +gab who authored the change and +dpranke who reviewed it.

Ah. This is no longer a master configuration issue, this is an MB configuration issue :).

When we moved the builder we didn't update mb_config.pyl.

https://codereview.chromium.org/2618643002/

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e2730358eadd0dc68d4da80bab44401c33ed6aac

commit e2730358eadd0dc68d4da80bab44401c33ed6aac
Author: dpranke <dpranke@chromium.org>
Date: Thu Jan 05 03:48:28 2017

Update MB entries for the Linux TSAN Builder.

We moved the builder from the memory.full waterfall to the
memory waterfall but forgot to update the MB config file.

Also, re-sort the builder names in the memory waterfall entries.

TBR=gab@chromium.org
BUG= 676842 

Review-Url: https://codereview.chromium.org/2618643002
Cr-Commit-Position: refs/heads/master@{#441575}

[modify] https://crrev.com/e2730358eadd0dc68d4da80bab44401c33ed6aac/tools/mb/mb_config.pyl

The bot still red:
https://build.chromium.org/p/chromium.memory/waterfall?builder=Linux%20TSan%20Builder
is this bug still 'started'?

The bot has cycled green:

https://build.chromium.org/p/chromium.memory/builders/Linux%20TSan%20Builder/builds/698

@loyso - I think you clicked on things slightly too early, and the first build w/ my fix hadn't cycled through yet (the build above completed ~10 minutes after your comment :).

Thanks Dirk!

PS: maybe it's just me but configuring these feels like a game of whack-a-mole :(...

Yup, no argument there ...