Closed
Bug 903462
Opened 11 years ago
Closed 11 years ago
Please investigate r4-lion slaves
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
References
Details
This slave isn't responding to PDU reboots.
Reporter | ||
Comment 1•11 years ago
|
||
More than one lion slave in this state, so adding them all as blockers. This *may* be a result of netboots in bug 891880.
Summary: Please investigate talos-r4-lion-005 → Please investigate r4-lion slaves
Reporter | ||
Updated•11 years ago
|
Blocks: talos-r4-lion-028, talos-r4-lion-030
Comment 2•11 years ago
|
||
Have these all already been netbooted? I don't see anything in the DeployStudio activity view, but it times hosts out after they finish a workflow, so that doesn't necessarily tell me much.
Comment 3•11 years ago
|
||
Talos-r4-lion-005 was taken offline to run diagnostics.
Reporter | ||
Comment 4•11 years ago
|
||
Dustin: all of batch #1 (001-030) were blessed and rebooted earlier in the week (Tuesday), so they *should* have come back.
Updated•11 years ago
|
colo-trip: --- → scl1
Comment 5•11 years ago
|
||
All hosts were in powered off state. Once we turned them on, netboot automatically kicked. All hosts (excluding talos-r4-lion-005) are back online. Lion-005 still being investigated per bug 902970.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•