helium/potassium are still on precise, should be upgraded to trusty (as the pool counters in codfw) or reinstalled with jessie. Needs to be done carefully, as the non-availability of pool counters causes problems.
|operations/mediawiki-config : master||Put back potassium as poolcounter1002|
|operations/puppet : production||Rename potassium as poolcounter1002|
|operations/dns : master||Rename potassium as poolcounter1002|
|operations/mediawiki-config : master||Put helium back in service during potassium reimage|
|operations/mediawiki-config : master||Replace helium with poolcounter1001|
|operations/puppet : production||Provision poolcounter1001|
|operations/dns : master||eqiad: add poolcounter1001|
|operations/mediawiki-config : master||deployment-prep: Move poolcounter to deployment-poolcounter04|
|operations/puppet : production||poolcounter: move to modules/role|
|Resolved||Dzahn||T123525 reduce amount of remaining Ubuntu 12.04 (precise) systems in production|
|Resolved||fgiunchedi||T123734 Migrate pool counters to trusty/jessie|
|Resolved||fgiunchedi||T146277 Build poolcounter for jessie|
|Resolved||Cmjohnson||T149106 Rename potassium / WMF3287 as poolcounter1002|
for one of the pool counters, it probably makes sense to move it to a ganeti VM. requirements are minimal for a pool counter anyway, it's a perfect candidate for virtualization. I am saying for one only because we want the 2 of them to be in different rows and our ganeti cluster still is one row only.
I tried provisioning deployment-poolcounter03 with jessie to migrate beta too but ATM the instance is not accessible via ssh and console shows
Debian GNU/Linux 8 deployment-poolcounter03 ttyS0 deployment-poolcounter03 login: 2016-10-03T09:52:06.250841+00:00 deployment-poolcounter03 nslcd:  <passwd="filippo"> (re)loading /etc/nsswitch.conf 2016-10-03T09:53:22.827801+00:00 deployment-poolcounter03 puppet-agent: Could not request certificate: getaddrinfo: Name or service not known 2016-10-03T09:55:22.839435+00:00 deployment-poolcounter03 puppet-agent: Could not request certificate: getaddrinfo: Name or service not known 2016-10-03T09:57:22.846457+00:00 deployment-poolcounter03 puppet-agent: Could not request certificate: getaddrinfo: Name or service not known
We talked about this briefly and agreed that "germanium" is free and can be used to avoid reusing a name. The VMs for PCI scanning _might_ be re-created one day and reusing names caused unexpected issues and confusion before.