[05:19] -queuebot:#ubuntu-release- New binary: python-pip [amd64] (jammy-proposed/universe) [21.3.1+dfsg-3] (i386-whitelist)
[05:23] -queuebot:#ubuntu-release- New binary: wheel [amd64] (jammy-proposed/universe) [0.37.1-2] (i386-whitelist)
[05:23] -queuebot:#ubuntu-release- New binary: setuptools [amd64] (jammy-proposed/main) [59.6.0-1.1] (core, i386-whitelist)
[08:31] <ricotz> hello, could some please kill the autopkgtest for 'libreoffice/1:7.3.0~rc1-0ubuntu0.22.04.1~lo2' on jammy/arm64
[08:47] -queuebot:#ubuntu-release- New: accepted python-pip [amd64] (jammy-proposed) [21.3.1+dfsg-3]
[08:47] -queuebot:#ubuntu-release- New: accepted wheel [amd64] (jammy-proposed) [0.37.1-2]
[08:47] -queuebot:#ubuntu-release- New: accepted setuptools [amd64] (jammy-proposed) [59.6.0-1.1]
[09:23] <laney> juliank: I lost your ping somehow before I could read it, sorry. how can I help?
[09:23] <laney> I broke my irssi colours somehow and channels with highlights now don't get a special colour
[09:23] <juliank> laney: nevermind, it's all good now
[09:23] <laney> it's annoying
[09:23] <laney> okay
[09:23] <laney> having some fun with the armhf workers?
[09:24] <laney> I wanted to get to auto-recycling of those at some point, they just tended to go south after a few weeks
[09:26] <laney> or get armhf working on cloud, xnox seemed to think that was (close to) working at one point
[09:26] <juliank> laney: yeah, I'm currently rewriting cleanup-lxd in python to just um only keep the newest 3 containers and delete everything else
[09:26] <laney> heh
[09:26] <juliank> because it keeps accumulating dead containers :D
[09:26] <laney> sometimes I saw the API just stop responding though
[09:26] <juliank> I deleted all of them yesterday, but 153 already has 20 or so
[09:26] <laney> so deletions would just hang forever
[09:27] <juliank> well
[09:27] <laney> make sure to have a timeout / make it email you or something
[09:27] <juliank> timeout is fine, yeah
[09:27] <juliank> it times out on the tcp level at 30s anyway
[09:27] <juliank> and it runs hourly
[09:27] <juliank> considered moving this to the indvidiual lxd hosts rather tha ndoing it over network too
[09:27] <juliank> but ... later
[09:28] <laney> this stuff really "should" all be reliable
[09:28] <laney> any idea why they are being left behind, autopkgtest not deleteing them?
[09:37] <juliank> laney: haven't actually looked at the logs from the past 14 hours yet, but I also hacked around using stop instead of delete, which might have caused some containers to end up stopped rather than deleted
[09:37] <juliank> as delete always had a 30s stop timeout
[09:37] <juliank> There's a cool email on ubuntu-devel with everything that happened so far :)
[09:39] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (impish-proposed) [2.54.2+21.10]
[09:41] <juliank> non-zero exit status -15
[09:41] <juliank> what?
[09:43] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (hirsute-proposed) [2.54.2+21.04]
[09:44] <laney> nice about the subvolume discovery
[09:45] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (focal-proposed) [2.54.2+20.04]
[09:49] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.54.2+18.04]
[09:52] <juliank> laney:  the new cleanup-lxd is fancy too https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/tools/cleanup-lxd
[09:52] <juliank> well fancier :D
[09:54] <juliank> let's bring the new node up
[09:55] <juliank> (the timeout is actually in the service invoking cleanup-lxd)
[09:56] <juliank> time to redeploy lxd-armhf9
[09:56] <juliank> it had disk I/O errors
[09:56] <laney> nice
[09:57] <laney> do you still have that thing where you need to keep trying a deploy until you get one of the fast machines?
[09:57] <laney> because swirlix
[09:57] <laney> or did they take those out?
[09:58] <juliank> still doing that
[09:58] <laney> sad face
[10:00] <juliank> first try worked :D
[10:03] <juliank> to be honest instead of the lxd controller worker in prodstack, I'd just have each lxd worker do the amqp dance itself and save the network between them
[10:03] <juliank> but oh well
[10:06] <laney> it's scalingstack and firewall stuff, nodes running untrusted workloads
[10:06] <juliank> yeah
[10:07] <laney> one of my ideas about 5 years ago, which I did start exploring, was to use LXD for everything unless it had the isolation-machine restriction
[10:07] <laney> be thankful I never carried on with that :D
[10:10] <juliank> heh
[10:11] <juliank> I need to setup RAM and CPU limits for lxd, such that they behave more like the vms
[10:11] <juliank> wrt big_packages
[10:12] <laney> good idea, shouldn't be too hard to do
[10:12] <juliank> Yeah, set default profile to default limits, add a big profile, and then set profile from the autopkgtest-virt-lxd script
[10:16] <laney> how's the state of monitoring/alerting on autopkgtest-cloud stuff, still just relying on people noticing?
[10:16] <juliank> yeah
[10:20] -queuebot:#ubuntu-release- Unapproved: network-manager (focal-proposed/main) [1.22.10-1ubuntu2.2 => 1.22.10-1ubuntu2.3] (desktop-core, i386-whitelist)
[10:39] <juliank> I restarted lxd-armhf10 as it missed to reboot during setup and hence did not have compat_uts_machine=armv7l set
[10:39] <juliank> the new lxd-armhf9 is active now as well
[10:41] <juliank> oops
[10:41] <juliank> i ran mojo while having scalingstack sourced causing it to not find ips of frontend server
[10:41] <juliank> lalalala
[11:36] <RikMills[m]> .
[12:24] <sil2100> juliank: you're still all busy with ADT infra I suppose?
[12:36] <juliank> sil2100: about to eat lunch and then talk grub
[13:41] <sil2100> juliank: \o/ I had a grub thing actually, so this thing came up recently: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046
[13:42] <sil2100> I don't think it actually has any ill-effect though, but I see Dann prepared a fix last year
[13:42] <juliank> sil2100: it will happen _after_ riscv64
[13:42] <sil2100> Excellent
[13:42] <juliank> sil2100: because riscv64 is in progress and they touch the same code, so conflicts!
[13:42] <sil2100> Ouch!
[13:43] <sil2100> Yeah, riscv64 is also important, crucial to the installer work
[15:08] -queuebot:#ubuntu-release- New binary: ntfs-3g [amd64] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[15:08] -queuebot:#ubuntu-release- New binary: ntfs-3g [s390x] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[15:09] -queuebot:#ubuntu-release- New binary: ntfs-3g [ppc64el] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[15:10] <juliank> vorlon: so half of the tests in the 16:05 report window failed (13/26), websocket errrors and Error: Post "https://10.44.124.15:8443/1.0/instances/autopkgtest-lxd-vhxpqd/exec": x509: certificate is valid for 127.0.0.1, ::1, not 10.44.124.15
[15:11] <juliank> vorlon: Not sure if this is persistent or just a lxd snap that upgraded itself
[15:15] -queuebot:#ubuntu-release- New binary: ntfs-3g [arm64] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[15:15] -queuebot:#ubuntu-release- New binary: ntfs-3g [armhf] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[15:41] -queuebot:#ubuntu-release- New binary: ntfs-3g [riscv64] (jammy-proposed/main) [1:2021.8.22-3ubuntu1] (core)
[16:55] <vorlon> juliank: any improvement?
[16:56] <juliank> vorlon: didn't happen again
[16:56] <juliank> everything looks happy
[17:38] -queuebot:#ubuntu-release- New binary: imath [amd64] (jammy-proposed/universe) [3.1.3-6] (no packageset)
[17:39] -queuebot:#ubuntu-release- New: accepted imath [amd64] (jammy-proposed) [3.1.3-6]
[17:41] -queuebot:#ubuntu-release- New binary: imath [s390x] (jammy-proposed/universe) [3.1.3-6] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: imath [ppc64el] (jammy-proposed/universe) [3.1.3-6] (no packageset)
[17:47] -queuebot:#ubuntu-release- New: accepted imath [ppc64el] (jammy-proposed) [3.1.3-6]
[17:47] -queuebot:#ubuntu-release- New: accepted imath [s390x] (jammy-proposed) [3.1.3-6]
[17:58] -queuebot:#ubuntu-release- New binary: imath [armhf] (jammy-proposed/universe) [3.1.3-6] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: imath [arm64] (jammy-proposed/universe) [3.1.3-6] (no packageset)
[19:46] -queuebot:#ubuntu-release- New binary: bup [amd64] (jammy-proposed/universe) [0.32-3build2] (no packageset)
[22:10] -queuebot:#ubuntu-release- New binary: node-arr-exclude [amd64] (jammy-proposed/universe) [1.0.0-2] (no packageset)
[22:34] -queuebot:#ubuntu-release- New: accepted imath [arm64] (jammy-proposed) [3.1.3-6]
[22:34] -queuebot:#ubuntu-release- New: accepted node-arr-exclude [amd64] (jammy-proposed) [1.0.0-2]
[22:34] -queuebot:#ubuntu-release- New: accepted imath [armhf] (jammy-proposed) [3.1.3-6]