Closed Bug 1055416 Opened 11 years ago Closed 11 years ago

decom ftp7.dmz.scl3

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
Other
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nagiosapi, Unassigned)

References

(
URL
)

Details

(Whiteboard: [id=nagios1.private.scl3.mozilla.com:403781])

Automated alert report from nagios1.private.scl3.mozilla.com: Hostname: ftp7.dmz.scl3.mozilla.com State: DOWN Output: PING CRITICAL - Packet loss = 100%
Automated alert acknowledgement: (ashish)Bug 1055179
Status: NEW → ASSIGNED
Confusion here; bug 1036443 says it's decom'ed, bug 1055179 says it's a member of the cluster.
No, ftp7 is decomisionned, that's a fact. bug 1055179 just mis-spoke.
Cool, then. I'm not seeing a decom bug for ftp7 in the past and there's remnants, so let's make this one it. :)
Assignee: nobody → server-ops
Status: ASSIGNED → NEW
Component: Server Operations: MOC → Server Operations
QA Contact: dmoore → shyam
Summary: ftp7.dmz.scl3.mozilla.com is DOWN: PING CRITICAL - Packet loss = 100% → decom ftp7.dmz.scl3
10.22.74.77 Pulled from nagios, inventory. Not in rhn or puppetdashboard. Deleted from filer access list. Had flows, killed in bug 1060565. Not filing a dcops bug since it's a seamicro and the whole chassis will go away in due time.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.