Closed Bug 443301 Opened 17 years ago Closed 17 years ago

Reboot several talos machines

Categories

(mozilla.org Graveyard :: Server Operations, task, P2)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: sdwilsh, Assigned: phong)

References

Details

I'd like to see qm-mini-xp01, qm-mini-xp02, qm-mini-xp03, qm-pxp-trunk01, qm-pxp-trunk02, qm-pxp-trunk03, qm-pvista-trunk01, qm-pvista-trunk02, and qm-pvista-trunk03 rebooted. See bug 442949 for details.
Blocks: 442949
Build: Can this happen now? Do you need us to do this or can you handle it?
Assignee: server-ops → aravind
We need a scheduled downtime for this to happen, it will cause all those machines to go red on the Firefox and Mozilla2 waterfall.
Assignee: aravind → anodelman
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Talos
Priority: -- → P2
I've rebooted qm-mini-xp01/02/03 by working around the long PGO build times for the firefox 3 win build machine. This is as of 11am PDT.
Assignee: anodelman → bhearsum
Ok, I've rebooted all of them. qm-pxp-trunk01 did not come back up, so I'm passing this bug to IT. We have trunk02 and trunk03 though, so I don't think this is urgent.
Assignee: bhearsum → server-ops
Component: Release Engineering: Talos → Server Operations
Assignee: server-ops → phong
Status: NEW → ASSIGNED
Flags: colo-trip+
qm-pxp-trunk01 is up again.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.