Closed
Bug 781526
Opened 12 years ago
Closed 12 years ago
do prework to decommission releng-dashboard-sandbox1.vm.labs.scl3.mozilla.com
Categories
(Infrastructure & Operations Graveyard :: WebOps: Labs, task, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: cliang)
References
Details
(Whiteboard: [briarpatch])
releng-dashboard-sandbox1.vm.labs.scl3.mozilla.com is a vm used for development of briar-patch. administrative ownership has been transferred to hwine.
Chris Lonnen recommends we hang onto the machine for now until the next steps for briar-patch are clear. Filing this bug so we don't loose track of it.
Reporter | ||
Comment 1•12 years ago
|
||
briar patch is dead - this vm can be decommissioned.
Component: Release Engineering: Machine Management → Server Operations: RelEng
QA Contact: armenzg → arich
Comment 2•12 years ago
|
||
I think this one is for Gozer..
Assignee: hwine → server-ops-labs
Component: Server Operations: RelEng → Server Operations: Labs
QA Contact: arich → zandr
Assignee | ||
Updated•12 years ago
|
Assignee: server-ops-labs → cliang
Reporter | ||
Comment 3•12 years ago
|
||
Box has been taken offline, but alerts still active:
Subject: ** PROBLEM alert -
releng-dashboard-sandbox1.vm.labs.scl3.mozilla.com/ is DOWN **
From: labs-shared@mozilla.com
To: hwine@mozilla.com
Message-Id: <20121030202709.2C03A379C9@shinken1.localdomain>
Date: Tue, 30 Oct 2012 13:27:09 -0700 (PDT)
***** Shinken Notification *****
Notification: PROBLEM
Service:
Host: releng-dashboard-sandbox1.vm.labs.scl3.mozilla.com
Address: 10.22.112.118
State: DOWN
Date/Time: 30-10-2012
Additional Info: PING CRITICAL - Packet loss = 100%
Assignee | ||
Comment 4•12 years ago
|
||
Huh. Setting this host into down time did not block this alert. I've manually deleted the host from monitoring and confirmed that the automated processes don't add it back in.
Comment 5•12 years ago
|
||
Is the box dead for sure and not breathing and can we purge the flows to/from it?
Comment 6•12 years ago
|
||
KILL
Assignee | ||
Comment 7•12 years ago
|
||
Typically, I turn off the VM, disable active monitoring, then wait a month before doing anything more drastic (like remove DNS entries). If its an issue, we could purge the flows to/from it as long as they are clearly documented somewhere (in case we suddenly need to add them back in).
Comment 8•12 years ago
|
||
Let's go the usual way and leave it for a month - so nothing breaks. I have it noted anyway in my SCL3 review so will re-ping in a few weeks. Thanks!
Assignee | ||
Comment 9•12 years ago
|
||
- The ACL flows for this machine have been removed.
- The networking entries have been removed from inventory.
- The DNS entries for this VM have been removed.
- I've taken a backup export of the VM and am moving it to a location where it should end up being backed up to tape.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•8 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•