Closed Bug 644243 Opened 15 years ago Closed 15 years ago

re-image w32-ix-slave01

Categories

(Release Engineering :: General, defect, P3)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: dustin)

References

Details

(Whiteboard: [slaveduty][opsi])

'buildbot start' fails with this error: ImportError: No module named buildbot.scripts
Same error is in /c/tmp/buildbot-sh-startup.log. I suspect an OPSI failure.
Yep, OPSI has "buildbot-production" marked as FAILURE. I marked it as "setup" in the UI and rebooted, and it went right back to FAILURE. I checked the opsi event log and didn't see anything referencing this package. The BUILDBOT_PRODUCTION tag still exists and still points to a revision from May 2010, so the recent changes to buildslave versions have not caused this. I'm not sure what to do other than reimaging the machine. Other ideas?
Whiteboard: [slaveduty] → [slaveduty][opsi]
Let's re-image it. Not that that will make OPSI behave better.
Assignee: nobody → server-ops-releng
Component: Release Engineering → Server Operations: RelEng
QA Contact: release → zandr
Summary: buildbot on w32-ix-slave01 doesn't work → re-image w32-ix-slave01
Assignee: server-ops-releng → arich
Server has been reimaged, passing back to release for additional configuration if required.
Assignee: arich → release
Assignee: release → release
This was sitting in the RelOps queue, over to RelEng to either a) return to service, or b) assign to iX batch III.
Assignee: release → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Assignee: nobody → dustin
returned to service.
Status: NEW → RESOLVED
Closed: 15 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.