If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

w32-ix-slave34 has the wrong buildbot version

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: armenzg, Assigned: dustin)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [slaveduty][buildslaves])

(Reporter)

Description

6 years ago
C:\Documents and Settings\cltbld>buildbot --version
Buildbot version: 0.7.10p1
Twisted version: 2.5.0

I noticed this by looking at the remote_getVersion exceptions from the masters.

Comment 1

6 years ago
Disabled.
Priority: -- → P3
Whiteboard: [slaveduty] → [slaveduty][badslave?]
(Assignee)

Updated

6 years ago
Assignee: nobody → dustin
Whiteboard: [slaveduty][badslave?] → [slaveduty][buildslaves]
(Assignee)

Comment 2

6 years ago
fix will be in bug 661758.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

6 years ago
As noted in bug 661758, this machine didn't get the right packages from OPSI on its reimage, and is now hopelessly wedged.  I'm going to re-image it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 4

6 years ago
So one key point I forgot in this was to change the machine name.  After that, OPSI seems to have done most of the work.  We'll see if it updates nsc.ini or not, a la w32-ix-slave07 and 08.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 5

6 years ago
Many w32 ix machines have been having issues in the last few months. Several of them will be reimaged and setup correctly in bug 682408.

Particularly slave w32-ix-slave34 was being setup again but will be reimaged after a new snapshot as part of bug 682408's work.
Blocks: 682408
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.