Retire gitlab-dev-01

This machine was brought up from backups as a (successful) proof of concept. Now, we realize the machine might have apparently been interacting with CI and accumulating data beyond normal limits, so Nagios is starting to complain. Also, the usefulness of keeping is around isn't really established: we might have had use for it in gitlab#23 (closed) until we realized that if we flip the switch on mail on that server, this could potentially unleash a torrent of irrelevent notifications on many unsuspecting users.

1. announcement
2. nagios
3. retire the host in fabric
4. remove from LDAP with ldapvi
5. power-grep
6. remove from tor-passwords
7. remove from DNSwl
8. remove from docs
9. remove from reverse DNS

added Gitlab lifecycle labels

assigned to @lavamind

added Backlog label

mentioned in issue #41146 (closed)

marked this issue as related to #40794 (closed)

mentioned in issue #40794 (closed)

added Doing label and removed Backlog label

marked the checklist item announcement as completed

changed due date to June 05, 2023

marked the checklist item nagios as completed

Announcement sent, retirement scheduled for next Monday.

added Next label and removed Doing label

added Doing label and removed Next label

marked the checklist item retire the host in fabric as completed

marked the checklist item remove from LDAP with ldapvi as completed

mentioned in commit wiki-replica@b61ad638

marked the checklist item power-grep as completed

marked the checklist item remove from tor-passwords as completed

marked the checklist item remove from docs as completed

marked the checklist item remove from reverse DNS as completed

marked the checklist item remove from DNSwl as completed

All done, box retired.

closed

we're getting daily warnings from bacula, it seems the machine wasn't properly retired.

reopened

Done for good this time:

 ./retire -v -H gitlab-dev-01.torproject.org retire-all --parent-host=dal-node-01.torproject.org
--verbose is now deprecated and the default
starting tasks at 2023-06-07 15:51:59.357501+00:00
checking for ganeti master on host dal-node-01.torproject.org
ganeti node detected with master dal-node-01.torproject.org
checking on dal-node-01.torproject.org if instance gitlab-dev-01.torproject.org is running
instance gitlab-dev-01.torproject.org not running, no stop required
scheduling gitlab-dev-01.torproject.org instance removal on host dal-node-01.torproject.org
scheduling gnt-instance remove --force gitlab-dev-01.torproject.org to run on dal-node-01.torproject.org in 7 days
warning: commands will be executed using /bin/sh
job 4 at Wed Jun 14 15:52:00 2023
scheduling gitlab-dev-01.torproject.org backup disks removal on host bungei.torproject.org and director bacula-director-01.torproject.org
checking for path "/srv/backups/bacula/gitlab-dev-01.torproject.org/" on bungei.torproject.org
scheduling rm -rf "/srv/backups/bacula/gitlab-dev-01.torproject.org/" to run on bungei.torproject.org in 30 days
warning: commands will be executed using /bin/sh
job 103 at Fri Jul  7 15:52:00 2023
checking for path "/srv/backups/pg/gitlab-dev-01/" on bungei.torproject.org
path /srv/backups/pg/gitlab-dev-01/ not found: [Errno 2] No such file
scheduling echo delete client=gitlab-dev-01.torproject.org-fd yes | bconsole to run on bacula-director-01.torproject.org in 30 days
warning: commands will be executed using /bin/sh
job 55 at Fri Jul  7 15:52:00 2023
Notice: Revoked certificate with serial 156
Notice: Removing file Puppet::SSL::Certificate gitlab-dev-01.torproject.org at '/var/lib/puppet/ssl/ca/signed/gitlab-dev-01.torproject.org.pem'
gitlab-dev-01.torproject.org
Submitted 'deactivate node' for gitlab-dev-01.torproject.org with UUID befc54fa-de27-4359-a405-05d282c2c0c2
completed tasks, elasped: 0:00:17.846891 (user 4.77 system 0.12 chlduser 0.0 chldsystem 0.0 RSS 46.7 MB)

And removed the duplicate at job on dal-node-01.

closed