Closed Bug 673013 Opened 14 years ago Closed 14 years ago

Move 12 win32 ix machines from production to try

Categories

(Release Engineering :: General, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: catlee)

Details

Attachments

(2 files, 1 obsolete file)

Need to: * disable slaves in slavealloc * gracefully shutdown the slave * change ssh keys * move slaves to try in slavealloc * reboot
We're going to be doing mw32-ix-slave{12..18} and w32-ix-slave{02..08, 22}
Attachment #547463 - Flags: review?(bhearsum)
Assignee: nobody → catlee
Priority: -- → P2
Attachment #547473 - Flags: review?(bhearsum)
we're doing w32-ix-slave{02..04,07..08,22..24} now since 5,6 were already on try.
Priority: P2 → --
Attachment #547473 - Flags: review?(bhearsum) → review+
Attachment #547463 - Attachment is obsolete: true
Attachment #547463 - Flags: review?(bhearsum)
mw32-ix-slave{12..18} are now connected to bm09-try1
Priority: -- → P2
w32-ix-slave{07,24} are still running on bm6 (buildbot-master5) & bm12-build1. I will check later to reconfigure the masters and put the slaves in the pool.
I have reconfigured those 2 masters as well and setup those 2 slaves for the try server. I will check my slaves in the morning.
w32-ix-slave02 fix buildbot version w32-ix-slave03 just pingable - try IPMI w32-ix-slave23 down - iX repairs - bug 655304 I truly believe I did slaves 03 & 23 but if I can't reach them now how did I do it? I added a note before they get re-enabled. I missed this slave: w32-ix-slave07 added try keys, enabled and rebooted
(In reply to comment #8) > w32-ix-slave02 fix buildbot version bug 673415 > w32-ix-slave03 just pingable - try IPMI bug 673414
Comment on attachment 547473 [details] [diff] [review] slave shuffle in production_config.py Landed Jul 21: http://hg.mozilla.org/build/buildbot-configs/rev/2fe726f9416a
Attachment #547473 - Flags: checked-in+
w32-ix-slave04 is sitting idle, disabled in slavealloc. Ready to go ?
(In reply to Nick Thomas [:nthomas] from comment #11) > w32-ix-slave04 is sitting idle, disabled in slavealloc. Ready to go ? I probably forgot. I am clobbering it, I will adjust slavealloc and will reboot it (the try keys are already in here).
I adjusted everything on slavealloc except the "enable" flag. Rebooted again and will check tomorrow.
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #13) > I adjusted everything on slavealloc except the "enable" flag. Rebooted again > and will check tomorrow. I had to redeploy runslave.py as it seem that it had an older version (it should have ensured that basedir existed and created it if not). OPSI...
I'm going to move 4 of these back to the production pool. mw32-ix-slave{12..14}
(In reply to Chris AtLee [:catlee] from comment #15) > I'm going to move 4 of these back to the production pool. > > mw32-ix-slave{12..14} make that mw32-ix-slave{12..15)
Attachment #552643 - Flags: review?(bhearsum)
Attachment #552643 - Flags: review?(bhearsum) → review+
Attachment #552643 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 14 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.

Attachment

General

Created:
Updated:
Size: