[07:42:37] <elukey>	 hello folks!
[07:42:49] <elukey>	 I am going to merge https://gerrit.wikimedia.org/r/c/operations/puppet/+/1059899 and test a commit in the private puppet repo
[07:42:58] <elukey>	 if you need to do any work on it, ping me first please :)
[07:53:06] <elukey>	 tested a commit and it worked nicely
[07:54:09] <elukey>	 and now running manually dump_cloud_ip_ranges.service
[07:56:12] <elukey>	 it doesn't have anything to commit, will wait for the next run
[07:56:21] <elukey>	 all green from my side, if you encounter any issue with puppet private lemme know
[08:09:15] <dcausse>	 o/ I have a wdqs host (wdqs1023.eqiad.wmnet) that is misbehaving and needs to be depooled (it's causing maxlag errors on wikidata) but I can't access it via ssh, could someone maybe powercycle it so that I can try to depool it?
[08:11:30] <elukey>	 dcausse: sure on it
[08:11:40] <dcausse>	 elukey: thanks! <3
[08:12:22] <elukey>	 depooled as starter
[08:14:20] <elukey>	 dcausse: attached to the management console, and I see a ton of prints related to wdqs-categories
[08:14:30] <elukey>	 do you need details about it, or just a reboot?
[08:14:51] <dcausse>	 elukey: just a reboot I think
[08:15:10] <elukey>	 okok, the prints are all about hewiki btw
[08:16:28] <elukey>	 rebooting now
[08:20:10] <dcausse>	 elukey: when you depooled, did it print the pools it was attached to?
[08:20:41] <dcausse>	 this host just got re-imaged and is not supposed to serve traffic yet
[08:21:20] <elukey>	 dcausse: ah okok I see, I tried to confctl get and it doesn't show me anything
[08:21:24] <elukey>	 I thought it was in service
[08:21:30] <elukey>	 anyway, ready for you now
[08:21:35] <dcausse>	 elukey: thanks!
[08:25:30] <dcausse>	 ah I think I know why... some monitoring queries are polluting the metrics we use to detect if a host is live...
[12:11:59] <elukey>	 hello on-callers
[12:12:51] <elukey>	 as FYI I am going to stop debmonitor-server on debmonitor1003 for ~5 mins, to test if we can use debmonitor2003 instead (on a test node with a modified /etc/hosts)
[12:13:15] <elukey>	 so far it seems that only one django/debmonitor can be writing to the db, so I want to be sure about it
[12:13:37] <elukey>	 there may be a couple of failures here and there, nothing dramatic since the next runs of debmonitor clients will solve the issue
[12:17:23] <elukey>	 done, sigh the test failed, back to square one
[12:18:08] <XioNoX>	 :(
[14:22:03] <elukey>	 for the on-callers - I am going to upgrade debmonitor-server on debmonitor1003, new release version that fixes some issues and that will allow a more precise client to be rolled out
[14:22:20] <sukhe>	 elukey: ok :)
[14:28:44] <elukey>	 all good!
[14:28:55] <elukey>	 ping me in case you see anything weird
[14:29:08] <elukey>	 tomorrow I'll rollout the new version of the debmonitor-client as well