Closed
Bug 727977
Opened 13 years ago
Closed 13 years ago
Some win32 IX slaves have outdated mercurial version
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
Details
(Whiteboard: [buildduty][buildslaves])
it has hg 1.2.1, while others have 1.7.x
Probably need reimaging. disabled in slavealloc
Reporter | ||
Updated•13 years ago
|
Summary: mw32-ix-slave02 has outdated mercurial version → mw32-ix-slave02 and mw32-ix-slave20 have outdated mercurial version
Comment 1•13 years ago
|
||
mw32-ix-slave02 had a reimage as part of bug 702362, in late 2011
mw32-ix-slave20 had a reimage as part of the debugging in bug 682931, in Aug 2011.
win32-ix-ref has hg 1.2.1 in /d/mozilla-build/hg/, despite opsi saying that 1.7.5 is installed. There's something even older in /d/mercurial/ to get confused by.
Doing more of an audit using staging_config.py (trying to get a superset of all slaves) yields these ones on 1.2.1 (unless noted):
mw32-ix-slave05
mw32-ix-slave08
mw32-ix-slave19 (staging, v1.5.4)
mw32-ix-slave21 (staging)
mw32-ix-slave26
w32-ix-slave01 (staging, v1.5.4)
w32-ix-slave05 (staging)
w32-ix-slave07 (staging)
w32-ix-slave08 (staging)
w32-ix-slave23 (staging)
w32-ix-slave29
w32-ix-slave34
w32-ix-slave41
So it looks like we should
* update w32-ix-ref
* get the snapshot updated
* check if we need to clobber hg upgrades
* set the other slaves to re-install mercurial using opsi
* check what else hasn't been captured
Whiteboard: [buildduty][buildslaves]
Comment 2•13 years ago
|
||
So to make a complete list with corrected uses:
mw32-ix-slave05 (prod, v1.2.1)
mw32-ix-slave08 (prod, v1.2.1)
mw32-ix-slave19 (staging, v1.5.4)
mw32-ix-slave20 (prod, v1.5.4)
mw32-ix-slave21 (staging, v1.2.1)
mw32-ix-slave26 (prod, v1.2.1)
w32-ix-slave01 (staging, v1.5.4)
w32-ix-slave05 (try, v1.2.1)
w32-ix-slave07 (try, v1.2.1)
w32-ix-slave08 (try, v1.2.1)
w32-ix-slave23 (try, v1.2.1)
w32-ix-slave29 (prod, v1.2.1)
w32-ix-slave34 (prod, v1.2.1)
w32-ix-slave41 (prod, v1.2.1)
7 in prod, 4 in try, 3 in staging
Updated•13 years ago
|
Priority: -- → P3
Reporter | ||
Comment 3•13 years ago
|
||
I found that mw32-ix-slave08 and mw32-ix-slave21 don't have vs2010 installed. I believe that other slaves are out of date too. :/
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #1)
> * update w32-ix-ref
I'm going to update/install the following OPSI packages to the slaves, then to ix ref:
* vs2010
* mercurial
* mercurial-hgrc
* python-ssl
Reporter | ||
Comment 5•13 years ago
|
||
The following slaves have been synced and returned to production:
mw32-ix-slave02
mw32-ix-slave05
mw32-ix-slave20
mw32-ix-slave26
w32-ix-slave05
w32-ix-slave07
w32-ix-slave08
w32-ix-slave23
w32-ix-slave29
w32-ix-slave34
w32-ix-slave41
TODO:
mw32-ix-slave08 needs reimaging after repair? (bug 706947)
mw32-ix-slave21 loaned
w32-ix-slave01 still has 1.5.4 installed
mw32-ix-slave19 still has 1.5.4 installed
I think the root clause of all these problems is bug 730098 (win32-ix-ref cannot connect to production-opsi)
Reporter | ||
Updated•13 years ago
|
Summary: mw32-ix-slave02 and mw32-ix-slave20 have outdated mercurial version → Some win32 IX slaves have outdated mercurial version
Reporter | ||
Comment 6•13 years ago
|
||
mw32-ix-slave08 - Done
I filed bug 730400 as a followup for staging slaves.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•