Closed Bug 704475 Opened 14 years ago Closed 13 years ago

Return mw32-ix-slave08 to the production pool

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
x86
Windows Server 2003
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslaves])

The machine is ready for Ehsan to use. The password has been given to Ehsan. You might use this command to help you connect to the machine: ssh -L 5900:mw32-ix-slave08.build.mozilla.org:5900 build-vpn.mozilla.com
Priority: -- → P3
The IP is 10.250.49.181
Depends on: 704473
Thanks, eveything is working fine now. :-)
Depends on: 594474
No longer depends on: 594474
Depends on: 594474
Depends on: 704591
No longer depends on: 594474
I'm now done using this slave. Please do what needs to be done with it. Thanks!
Priority: P3 → --
In the future, we should be loaning out staging slaves rather than production ones.
(In reply to Ben Hearsum [:bhearsum] from comment #5) > In the future, we should be loaning out staging slaves rather than > production ones. This still needs to be re-imaged, correct?
OS: Mac OS X → Windows Server 2003
Priority: -- → P3
Summary: mw32-ix-slave08 is needed by Ehsan to debug failures in the Oak tree → Return mw32-ix-slave08 to the production pool
Whiteboard: [buildduty][buildslaves][waiting for reimage]
Depends on: 706947
This slave has been re-imaged and is ready to be puppetized.
Whiteboard: [buildduty][buildslaves][waiting for reimage] → [buildduty][buildslaves]
Looks like the slave was reimaged using a wrong ref image: mercurial 1.2.1, no vs2010...
(In reply to Rail Aliiev [:rail] from comment #8) > Looks like the slave was reimaged using a wrong ref image: mercurial 1.2.1, > no vs2010... Actually the ref machines was outdated, see bug 730098 for details.
Back to production
Status: NEW → RESOLVED
Closed: 13 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.