0c0240df
|
Antoine Beaupré
|
|
|
830cfe5f
|
Antoine Beaupré
|
|
|
bf64f10e
|
Antoine Beaupré
|
|
|
c0dc14e1
|
Antoine Beaupré
|
|
|
002f4212
|
Antoine Beaupré
|
|
|
b98a7340
|
Antoine Beaupré
|
|
|
113ed216
|
Jérôme Charaoui
|
|
|
227259eb
|
Jérôme Charaoui
|
|
|
5e0c4175
|
Jérôme Charaoui
|
|
|
f67f7191
|
Antoine Beaupré
|
|
|
c4a09172
|
Antoine Beaupré
|
|
|
5557f3bd
|
Antoine Beaupré
|
|
|
b26044d9
|
Antoine Beaupré
|
|
|
14fa8b40
|
Antoine Beaupré
|
|
|
42b3b0d9
|
Antoine Beaupré
|
|
|
3c5cc7fc
|
Antoine Beaupré
|
|
|
b0b8fc04
|
Antoine Beaupré
|
|
|
1c4b93c8
|
Jérôme Charaoui
|
|
|
65a7cdeb
|
Antoine Beaupré
|
|
|
86018648
|
Antoine Beaupré
|
stop tracking Debian major releases in Nagios
This was previously used to track which machine had been upgraded, but
it's really error prone. Just doing this, I found at least one machine
where we forgot to update this file (gayi, still marked as stretch).
That information is also available in PuppetDB (and more accurate)
anyways. It's the datasource we use now to do reports on the upgrade
progress.
To track which host is running a given release, run this on the
PuppetDB host (currently pauli):
curl -s -G http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { facts { name = "lsbdistcodename" and value = "buster" }}' | jq -r .[].certname
The above will show "buster" nodes, for example.
It's also pretty useless: we could, in theory, use this to (say)
acknowledge all problems matching a given OS, but in practice I have
never done this in three years so far, and it's not because I didn't
know about this group.
So, automation wins here: less churn and manual changes is good. If we
eventually reimplement this in Puppet, we could, in theory, restore
this group, but I don't even think *that* is worth it.
See also tpo/tpa/team#32901.
|
|