[09:02:28] <marostegui>	 phabricator is super slow, is that just me?
[09:24:58] <effie>	 it is ok gere
[09:25:00] <effie>	 here*
[09:25:57] <effie>	 slyngs: the alert is from a release that servers little to no traffic, nothing impactful for now, I will take a look what is up 
[09:39:48] <effie>	 the mw-api-ext-next deployment has 1 replica, and the workers got too busy, and it got a series of memcached errors https://logstash.wikimedia.org/goto/05cb6715157c9bea1f657931762996e5
[09:41:34] <effie>	 impact was minimal, however those memcached errors are tracked in https://phabricator.wikimedia.org/T420223
[09:44:03] <effie>	 those errors came from the simple health checks, so that is not great to page 
[13:20:42] <inflatador>	 <o/
[14:08:15] <vgutierrez>	 moritzm: if you have a sec I could use your aptrepo skills
[14:08:42] <vgutierrez>	 on https://haproxy.debian.net/pool/main/h/haproxy/haproxy_3.2.15-1~bpo13%2B1_amd64.deb I'm seeing that haproxy 3.2.15 is available for trixie but checkupdates on apt1002 doesn't agreee
[14:09:00] <vgutierrez>	 vgutierrez@apt1002:~$ sudo -i reprepro --component thirdparty/haproxy32 list trixie-wikimedia
[14:09:00] <vgutierrez>	 trixie-wikimedia|thirdparty/haproxy32|amd64: haproxy 3.2.14-1~bpo13+1
[14:09:01] <vgutierrez>	 vgutierrez@apt1002:~$ sudo -i reprepro --component thirdparty/haproxy32 checkupdate trixie-wikimedia
[14:09:01] <vgutierrez>	 Nothing to do found. (Use --noskipold to force processing)
[14:10:09] <vgutierrez>	 dunno if it could be related to the fact that fab.fur uploaded 3.2.14 manually instead of using reprepro update
[14:13:47] <taavi>	 vgutierrez: the update block is missing from distributions-wikimedia
[14:15:16] <vgutierrez>	 sigh.. nice catch, thanks
[14:17:32] <vgutierrez>	 https://gerrit.wikimedia.org/r/c/operations/puppet/+/1268223 looks good?
[14:18:48] <taavi>	 yep