Closed Bug 566166 Opened 14 years ago Closed 14 years ago

buildslave/talos reboots 2010/05/15

Categories

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

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: jabba)

Details

qm-pubuntu-try06
qm-pubuntu-try14

These are all from bug 564217, perhaps they lost power/network at about 05-15-2010 14:50 PDT ?
talos-r3-fed64-021.build
talos-r3-fed64-022.build
talos-r3-fed64-023.build
talos-r3-fed64-024.build
talos-r3-fed64-025.build
talos-r3-fed64-026.build
talos-r3-fed64-027.build
talos-r3-fed64-028.build
talos-r3-fed64-029.build
talos-r3-fed64-030.build
talos-r3-fed64-031.build
talos-r3-fed64-032.build
talos-r3-fed64-033.build
talos-r3-fed64-034.build
talos-r3-fed64-035.build
talos-r3-fed64-036.build
talos-r3-fed64-037.build
talos-r3-fed64-038.build
talos-r3-fed64-039.build
talos-r3-fed64-040.build
talos-r3-fed64-041.build
talos-r3-fed64-042.build
talos-r3-fed64-043.build
talos-r3-fed64-044.build
talos-r3-fed64-045.build
talos-r3-fed64-046.build
talos-r3-fed64-047.build
talos-r3-fed64-048.build
talos-r3-fed64-049.build
talos-r3-fed64-050.build
Component: Server Operations → Server Operations: Tinderbox Maintenance
Summary: buildslave/talos reboots 20100416 → buildslave/talos reboots 2010/05/15
Castro machines back online. Remaining at MPT:

qm-pubuntu-try06
talos-r3-fed64-019

qm-pubuntu-try08
qm-pubuntu-try14

moz2-win32-slave11 -- I realize this is a VM, but I can't seem to get this up&working from VNC, RDP, or VI, and I'm running out of consonants. :)
try-w32-slave20.build
(In reply to comment #3)
> try-w32-slave20.build

is a vm i now realize - so ignore this.
Castro machines rebooted and online.

Remaining @ MPT:

qm-pubuntu-try06
qm-pubuntu-try08

moz2-win32-slave11 (VM)
rebooted the rest.
Assignee: server-ops → jdow
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: colo-trip+
Resolution: --- → FIXED
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.