Closed
Bug 921008
Opened 11 years ago
Closed 11 years ago
Please decommission talos-r4-lion-045
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: achavez)
References
Details
(Whiteboard: [Waiting to be removed from nagios])
Multiple diagnostic runs have never turned up anything wrong with this slave, it has been re-imaged several times, yet it continues to burn jobs. Time to decommission it.
Updated•11 years ago
|
colo-trip: --- → scl1
Assignee | ||
Comment 1•11 years ago
|
||
talos-r4-lion-045 has been removed from dns and updated in inventory. arr: could you please remove from nagios?
Assignee: server-ops-dcops → achavez
Status: NEW → ASSIGNED
Whiteboard: [Waiting to be removed from nagios]
Comment 2•11 years ago
|
||
Looks like DNS got removed before the host was removed form the puppet nagios config (which causes puppet to fail on the nagios machine because it can't generate the actual nagios config). I've removed the host from nagios now. We should try to make sure to remove nagios before deleting DNS in the future to prevent puppet from breaking on the nagios host.
Assignee | ||
Comment 3•11 years ago
|
||
We'll definitely make sure to remove from nagios before deleting DNS, sorry about that! talos-r4-lion-045 has been removed from the rack.
Status: ASSIGNED → 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
•