[12:04] ubuntu-qa: I'm seeing plenty of "Traceback: The read operation timed out" when trying to queue autopkgtests. Is there anything we can do about it? [12:06] seems to be flaky [12:29] I think the HL is qa-help [12:38] yup. andersson1234 ^^ is that something you are already aware of? [12:40] I'm taking a look [12:42] okay, rabbitmq was restarted by our magical watchdog "maybe-restart-rabbitmq" about 10 minutes ago, that could explain the flakyness if it was almost dead [13:04] slyon: I don't see errors anymore, do you confirm that it's working on your side too? [13:05] Skia: seems to be working again for me [13:05] great [16:38] mattermost is down, so let's co-ordinate here if any fires need fighting :) [16:52] bdmurray: How often does update_excuses update? [16:53] andersson1234: hours [16:54] okay. noted [16:54] https://ubuntu-archive-team.ubuntu.com/proposed-migration/log/noble/2024-04-04/ [16:54] yeah, looks like its avergaing 2 or 2.5 hours [16:55] just so you know the current state, bos03 armhf workers 04 and 06 have been redeployed, but are still missing some LXD images. They both at least have noble, but can be taken down by other releases if bad scheduling happens. At least it's only a matter of restart, not redeploy. [16:55] missing images are in the process of being rebuilt, I'll keep monitoring that [16:56] Copy that. Thanks. [16:58] also, `~/juju-config/autopkgtest-lxd-worker_lxd-remotes.yaml` has up-to-date config, but not the service bundle yet, I'll push a commit soon with that [16:58] the advantage of the juju config file is that it has comments on the current status of remotes [17:05] we could make a script which produces yaml files for each juju config option, then our workflow could be: modify service bundle -> use script to produce the yaml files -> update config option with a juju config call [17:05] then we'd avoid having the yaml files and service bundle out of sync [17:06] I do really wonder if we can just use the service-bundle but with the right juju config options [17:08] 6 is all good, 4 is missing focal and mantic, in an retry loop for building; I've pushed the current config in the service-bundle on master, and now I'm dropping off; EOW o7 [17:08] forgot that: expect worker count at 29 [17:09] and the reported one in error in the KPI is a remain that didn't get cleaned up by `juju config`, but shouldn't exist anymore [17:25] `eod` see you tomorrow, and you on monday skia :)