Closed
Bug 639804
Opened 13 years ago
Closed 13 years ago
investigate why w32-ix-slave02 and w32-ix-slave04 are not configured correctly
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Assigned: dustin)
Details
(Whiteboard: [slaveduty][l10n])
Attachments
(1 file)
250 bytes,
patch
|
armenzg
:
review+
|
Details | Diff | Splinter Review |
both of these slaves have been burning l10n builds because they don't have proper ssh keys
Reporter | ||
Updated•13 years ago
|
Whiteboard: [slaveduty]
Comment 1•13 years ago
|
||
I thought these were staging slaves?
Reporter | ||
Comment 2•13 years ago
|
||
that would explain the ssh key error but beg the question of why they were assigned l10n nightly jobs
Comment 3•13 years ago
|
||
Have these two machines been officially moved to production? If so, it is then normal they could get assigned L10n jobs. FTR slave02 is not on OPSI as a production slave but slave04 is tracked as a production slave. http://hg.mozilla.org/build/opsi-package-sources/file/9126788ed78a/production-slaves#l228
Comment 4•13 years ago
|
||
Adding Pike so he is in the loop.
Whiteboard: [slaveduty] → [slaveduty][l10n]
Comment 5•13 years ago
|
||
There is also something to be noticed. slaves are not sorted so it could lead to visual confusion. w32-ix-slave41 offline w32-ix-slave42 connected w32-ix-slave01 offline w32-ix-slave02 connected w32-ix-slave03 connected w32-ix-slave04 The list ends and then it starts again. http://hg.mozilla.org/build/buildbot-configs/diff/0b1f39216424/mozilla/production_config.py
Assignee | ||
Comment 6•13 years ago
|
||
They were officially moved to production last week. I checked SSH keys on the hosts I set up, but I didn't set up all of them. I also moved them to production OPSI. Are the keys and OPSI fixed now? What's the current state?
Reporter | ||
Comment 7•13 years ago
|
||
no they need to be fixed, I was unable to connect to them using ssh or vnc (but I also only tried once). I pressed "graceful shutdown" on the master's web page for both of them.
Assignee | ||
Comment 8•13 years ago
|
||
OK, I logged in via RDP, disabled, and rebooted. That reboot may have burned a l10n build (hard to tell), but if so the build would have failed anyway.
Assignee | ||
Comment 9•13 years ago
|
||
w32-ix-slave04
Assignee: nobody → dustin
Attachment #517864 -
Flags: review?(armenzg)
Updated•13 years ago
|
Attachment #517864 -
Flags: review?(armenzg) → review+
Assignee | ||
Comment 10•13 years ago
|
||
comment 9 should ready "w32-ix-slave04 is already in the production list, so it doesn't need to be added. w32-ix-slave02 is back in production
Assignee | ||
Comment 11•13 years ago
|
||
w32-ix-slave04 is also back in production, with correct SSH keys.
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•