Given that the migration of Netbox to the nextbox dedicated hosts has been concluded and it's now running since a while and we're surely not coming back, we should cleanup the Netbox stuff from the netmon hosts unless they are scheduled to be reimaged soon.
A not complete list of things to cleanup:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| acme_chief: Revoke access from netmon boxes to netbox certificate | operations/puppet | production | +0 -1 |
Change 552680 had a related patch set uploaded (by Vgutierrez; owner: Vgutierrez):
[operations/puppet@production] acme_chief: Revoke access from netmon boxes to netbox certificate
Change 552680 merged by Vgutierrez:
[operations/puppet@production] acme_chief: Revoke access from netmon boxes to netbox certificate
Doing a quick check on netmon2001:
Okay I believe I have removed all traces on netmo1002 and netmon2001:
And rechecking the top list, I have removed acme certs, and other miscellany from /etc.
Any puppet code included in the netmon catalogs that is still referring netbox, if any.
Mentioned in SAL (#wikimedia-operations) [2019-11-28T13:21:31Z] <volans> cumin 'netmon*' 'rm -v /var/spool/cron/crontabs/postgres' T238919
Postgres user and related crontab are still present on the hosts and triggered a failure in the backup because there is no more DB to backup.
I've just removed the crontab for now.
I've also removed the crontab entries for wmf_auto_restart_uwsgi-netbox and prometheus-postgres-exporter.
Mentioned in SAL (#wikimedia-operations) [2019-11-28T13:28:22Z] <volans> cleanup root's crontab entries on netmon hosts from netbox/postres stuff - T238919
It looks like not all the puppet code was made ensure=>'absent'. We might have many more small things still laying around as a result.
I have done a survey of the hosts and I believe these nits are cleared up and cleaned.