Closed Bug 1024952 Opened 10 years ago Closed 10 years ago

Please decommission mm-ub-1204-32-temp.qa.scl3.mozilla.com

Categories

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

All
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Unassigned)

References

Details

(Keywords: spring-cleaning, Whiteboard: :VS [vm-delete:1])

On bug 828557 we setup this host for testing puppetagain. Meanwhile this os version is outdated and we don't want to support it anytime longer. Testing will happen on the new 14.04 machines we got via bug 999435.

So please decommission mm-ub-1204-32-temp.qa.scl3.mozilla.com.
Assignee: server-ops → dgarvey
Did not find the host in nagios "mm-ub-1204-32-temp.qa.scl3.mozilla.com" removed dns and deleted VM from inventory. This seems a little odd as I don't want to loose my reference in inventory;)
Not sure how I can check if the server is involved with zeus? 
Server not in RHN.
No puppet findings and therefore no foreman findings either.
Tried to login to 10.22.73.138 but can't login... It is not in puppet.
Assignee: dgarvey → server-ops
All this might be given that it is only a temporary host for testing. It is not in nagios.
I need to be able to login and checkout the filesystem. I need to determine if it is using nfs or other shared storage.
(In reply to dgarvey :dgarvey from comment #5)
> I need to be able to login and checkout the filesystem. I need to determine
> if it is using nfs or other shared storage.

It's not using any external file system, or shared storage. It's a plain system at the moment, which was kickstarted with the wrong deploy password. So simply remove it from vSphere, and get rid of any references to it.
Whiteboard: :VS
The list that :dgarvey was running is sort of a "hey did you think of this?" checklist is more tuned for the usual infra systems.  Here, (with some tribal knowledge of the system coming from :whimboo-as-owner and some allowances that QA's different), it's not as perfect of a fit.

I also restructured the checklist since this bug was first started, to be more of "gather info, turn it off, wait for screaming, really decom it" practice.  So:

10.22.73.138 = mm-ub-1204-32-temp.qa.scl3.mozilla.com
No nagios in infra.  No NFS or backups.  VM powered off.  Pausing to make sure there's no fallout, pick up the second half of the checklist in a week or two.
Keywords: spring-cleaning
Thanks Greg!
By the time I got here:
Not in DNS, not in inventory (maybe :dgarvey got 'em?).

Not in RHN because ubuntu.  Not in zeus or puppetdashboard because releng.
Nothing for netops or dcops.
Deleted VM from disk.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: :VS → :VS [vm-delete:1]
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.