647049 - figure out the status of SCL1 try masters then attach linux64-ix-slave 22,23,24,25,27,28,29,30,31,32,33,35,36,38,39

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

I don't know what is going on with these masters.  They have 15 slaves waiting for them as we want to avoid cross-dc buildbot sessions.  I have installed correct keys on these slaves and 

linux64-ix-slaveXX, where XX is

22,23,24,25,27,28,29,30,31,32,33,35,36,38,39

These slaves have baked in staging, are clobbered.  They need their buildbot.tac file renamed to buildbot.tac (from buildbot.tac.off) and to be rebooted.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

I suspect lukas can shed some light on this..

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

I am going to bring up the slaves as follows

22,23,24,25,27 - buildbot-master1:9013
28,29,30,31,32 - buildbot-master2:9013
33,35,36,38,39 - buildbot-master5:9012

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

Aside from slave 35 (648312), these machines made it into try last week

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Or, at least, the following made it into try just now:

linux64-ix-slave33
linux64-ix-slave34
linux64-ix-slave36
linux64-ix-slave38
linux64-ix-slave39

linux64-ix-slave26 is in the middle of a reimage (?); the rest are tracked in their own bugs.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

OK, linux64-ix-slave26 is having hardware problems - bug 651680.  So all of the reasonably functional linux64-ix slaves (25 of them) are running.