Closed Bug 1480570 Opened 7 years ago Closed 7 years ago

DECOM Request: mozdefqa2.private.scl3.mozilla.com

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: phrozyn, Assigned: alberto)

Details

Attachments

(1 file)

This request is for decomissioning of mozdefqa2.private.scl3.mozilla.com with IP of 10.22.75.177 This host is no longer needed. I'm not sure if it has any nagios monitoring. Feel free to forward to virtualization team if there is nothing more to do here.
Assignee: nobody → adelbarrio
Status: NEW → ASSIGNED
The host is not monitored by Nagios, according to the bot: •adelbarrio> Alberto del Barrio nagios-eis: status mozdefqa2.private.scl3.mozilla.com 2:16 PM <nagios-eis> adelbarrio: I'm sorry, I couldn't find any hosts/services for you. There are few references about "mozdefqa2" in Puppet: [alberto@banbao repos]$ grep -R mozdefqa puppet/* 2> /dev/null | cut -d':' -f 1 | sort | uniq puppet/hiera/nodes/syslog-dev1.private.mdc1.mozilla.com.yaml puppet/hiera/site.yaml puppet/manifests/nodes/proxy.pp puppet/modules/nagios4/files/prod/usr-local-bin/nagiosDashboardHosts puppet/modules/nagios4/files/prod/usr-local-bin/nagiosDashboardServices puppet/modules/nagios4/manifests/prod/eis/hostgroups.pp puppet/modules/nagios4/manifests/prod/eis/services.pp puppet/modules/opsec_base/files/heka.syslogng.toml Should those references be cleaned up? Other question: how can I know if puppet is running there? In case it is, how to stop it? Tried checking foreman but is not appearing there
Flags: needinfo?(rchilds)
(In reply to Alberto del Barrio from comment #1) > Should those references be cleaned up? Here's what I see, $ git grep "mozdefqa2" hiera/nodes/syslog-dev1.private.mdc1.mozilla.com.yaml: - 'mozdefqa2.private.scl3.mozilla.com' modules/nagios4/manifests/prod/eis/hostgroups.pp: 'mozdefqa2' => { modules/nagios4/manifests/prod/eis/hostgroups.pp: alias => 'mozdefqa2', modules/nagios4/manifests/prod/eis/services.pp: 'mozdefqa2', modules/nagios4/manifests/prod/eis/services.pp: 'mozdefqa2', modules/nagios4/manifests/prod/eis/services.pp: 'mozdefqa2', modules/nagios4/manifests/prod/eis/services.pp: 'mozdefqa2', And yes, these should be pulled > Other question: how can I know if puppet is running there? In case it is, > how to stop it? Tried checking foreman but is not appearing there Since this is an EIS host, it's more than likely not running Puppet
Flags: needinfo?(rchilds)
Attached file git diff
Attachment #8998757 - Flags: review?(rchilds)
I've deleted the references to the host from those files. I'm attaching a git diff, please Ryan review it. Also, I don't know what to do with this: 619 'check_mozdeflog' => { 620 service_description => 'MozDefBot log errors', 621 check_command => 'check_logwarn!/var/log/mozdef/mozdefbot.log!Traceback', 622 contact_groups => 'eisalertsonly, sysalertsonly', 623 max_check_attempts => 1, 624 hostgroups => $nagiosbot ? { 625 default => [ 626 'mozdefqa2', 627 ] 628 } 629 }, Should I remove the whole block? or maybe remove the part after "hostgroups => $nagiosbot?
Comment on attachment 8998757 [details] git diff LGTM
Attachment #8998757 - Flags: review?(rchilds) → review+
(In reply to Alberto del Barrio from comment #4) > Should I remove the whole block? or maybe remove the part after "hostgroups > => $nagiosbot? Remove that, it's a dupe of this in the same manifest, > 'check_mozdef_mozdefbot' => { > service_description => 'MozDef mozdefbot log errors', > check_command => 'check_logwarn!/var/log/mozdef/mozdefbot.log!Traceback', > contact_groups => 'eisalertsonly, sysalertsonly', > max_check_attempts => 1, > hostgroups => $nagiosbot ? { > default => [ > 'mozdef-alert', > ] > } > },
I pushed the changes in Puppet and going to proceed in few minutes to stop the host via vSphere
- Deleted DNS records from Infoblox - Marked as "Retired" in ServiceNow CMDB - Filled a bug to NetOps for ACL removal - Filled a bug to Virtualization for deleting the VM
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: