Bug 568268 tracks the re-purposing of the talos-try production slaves. Still to do: 1. Turn off talos-try and talos-staging-try masters 2. Re-purpose (if not used elsewhere): talos-rev1-xp01-04 talos-rev1-vista01-04 talos-rev1-tiger01-04 talos-rev2-leopard01-04 talos-rev1-linux01-05
Passing this along to John O'Duinn to deal with master removal & clean up.
Assignee: lsblakk → joduinn
From irc, these are so old and everything on new try-server-as-branch is so much better, there's nothing worth keeping here. No backups needed before deleting/recycling.
8 years ago
Depends on: 576418
(In reply to comment #3) > Bug 568268 tracks the re-purposing of the talos-try production slaves. > > Still to do: > > 1. Turn off talos-try and talos-staging-try masters > 2. Re-purpose (if not used elsewhere): > > talos-rev1-xp01-04 > talos-rev1-vista01-04 > talos-rev1-tiger01-04 Correct. > talos-rev2-leopard01-04 This should actually be "talos-rev1-leopard01-04" > talos-rev1-linux01-05 Correct.
(In reply to comment #4) > 1. Turn off talos-try and talos-staging-try masters lukas/anode: where exactly are these masters? By logging into one of the old rev1 slaves, I found they were connecting to talos-staging-master02.b.m.o. However, the master does not appear to be running, and I do see other buildbot masters running with rev3 minis. Please clarify which process (or which VM) I can find talos-try and talos-staging-try masters on?
Ok - I found and removed the buildbot master instances: talos-try-old on talos-master02 talos-staging-try on talos-staging-master02
The VMs are off. The work to bring collect these rev1 minis, and reimage them as buildbot testers is being tracked in bug#545249 and bug#576677. Nothing left to do here, so closing.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.