Closed Bug 686411 Opened 13 years ago Closed 13 years ago

reboot requests (sjc1)

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: phong)

Details

From bug 686394, bm-xserve04
try-mac-slave29
Assignee: server-ops-releng → mlarrain
colo-trip: --- → sjc1
moz2-darwin9-slave63
try-mac-slave02
g4-leopard01
try-mac-slave16 moz2-darwin9-slave03
moz2-darwin9-slave15
moz2-darwin9-slave58
try-mac64-slave17
Assignee: mlarrain → phong
not at sjc1: try-mac-slave29 g4-leopard01 won't power on: moz2-darwin9-slave03 try-mac-slave16 bm-xserve04
(In reply to Phong Tran [:phong] from comment #9) > not at sjc1: > try-mac-slave29 > g4-leopard01 Ben, Coop, these should have the correct DC suffix in nagios to make it easier to figure out where to file. I know these are low-priority, but it makes it hard to deliver reboots in a timely fashion when we're sent to the wrong DC :) I filed bug 688540 to track these mtv1 reboots. > won't power on: > moz2-darwin9-slave03 > try-mac-slave16 > bm-xserve04 Minis will be decommissioned: bug 688548 Xserve is undecided: bug 688561
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Alias: reboots-sjc1
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.