Closed Bug 636606 Opened 13 years ago Closed 13 years ago

win32-slave03 needs OPSI TLC

Categories

(Release Engineering :: General, defect, P4)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Unassigned)

Details

(Whiteboard: [slaveduty][buildslaves][opsi]) 

I can't, for the life of me, get OPSI to install buildbot on this newly-imaged slave.  I tried specifying the buildbot-production product as needing install, but the check step of that install fails because buildbot is not installed.  However, following those steps manually from the CMD.EXE prompt works fine.

After the hand-install, on reboot OPSI blew away my hand-installed work.  But a hand-installed version of buildbot isn't sustainable, anyway.

I'm out of options here.  I doubt sending the vm for re-imaging will help, since this is fresh back from a re-image.
According to the Machine Bookings page, win32-slave03 is meant to be a staging slave. Does that help at all?
OS: All → Windows Server 2003
Priority: -- → P3
Hardware: All → x86
no, doesn't particularly help, although since it's a staging VM it's certainly low priority.  It is a VM with a large disk, so apropos of bug 629377 we may want to get this fixed rather than trash it.  I just don't know how.
Priority: P3 → P4
Whiteboard: [slaveduty][buildslaves] → [slaveduty][buildslaves][opsi]
I'm deleting this box as mentioned above.
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.