Closed
Bug 863036
Opened 11 years ago
Closed 11 years ago
Please decommission talos-r3-fed-070
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
References
Details
(Whiteboard: Needs to be removed from rack and update inventory)
This slave (talos-r3-fed-070) is a repeat offender. Please run some diagnostics on it to see if there is an obvious culprit (memory, or logic board). If it's something we can diagnose and fix, great, otherwise let's decommission it.
Updated•11 years ago
|
colo-trip: --- → scl1
Updated•11 years ago
|
Whiteboard: running diagnostics
Comment 1•11 years ago
|
||
Hard drive was replaced last week for this host. Upon running a disk utility check, some errors were found and was advised to perform a "repair disk". I've ran the repair and reinstalled the OS for testing purposes. Now diagnostics came back clean without any errors. Will now reimage host. Let's give it one more shot.
Comment 2•11 years ago
|
||
Host has been reimaged to Fedora OS.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•11 years ago
|
||
This slave continues to be problematic. Let's just decomm it, please.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Please repair or decommission talos-r3-fed-070 → Please decommission talos-r3-fed-070
Comment 4•11 years ago
|
||
Host has been removed from DNS records. Still needs to be physically removed from rack and update inventory.
Updated•11 years ago
|
Whiteboard: running diagnostics → Needs to be removed from rack and update inventory
Talos-r3-fed-070 has been removed and the inventory has been updated.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 6•11 years ago
|
||
Please remember to either remove the host from nagios or pass off the bug to have it removed before closing.
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
•