Wednesday, 2023-06-21

-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul-jobs] 886552: Pin podman on jammy https://review.opendev.org/c/zuul/zuul-jobs/+/88655201:51
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 886432: Add ZK cache stats https://review.opendev.org/c/zuul/nodepool/+/88643201:52
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 886433: Limit TreeCache playback queue size https://review.opendev.org/c/zuul/nodepool/+/88643301:53
@harbott.osism.tech:regio.chatfwiw I'm having the same issue with rooms stuck unread. as a result I've completely muted this channel now06:58
@jjbeckman:matrix.orgAh, sorry for the confusion. I realised that "Git Driver" is only for public repositories and does not fit my use case at all. Thank you for the advice though.09:25
@yoctozepto:matrix.orgA little Zuul dissemination thrown-in by me at the end of the report: https://zenodo.org/record/8059779 enjoy!10:33
@fungicide:matrix.org> <@harbott.osism.tech:regio.chat> fwiw I'm having the same issue with rooms stuck unread. as a result I've completely muted this channel now12:20
at least in my case, i'm almost certain it's threads people keep replying in many pages back in my channel history. when i can find and expand them it shrinks or clears the unread count as desired, the ui just doesn't make it easy to find them
@yoctozepto:matrix.orgthe worst is it keeps the notification dot for threads I was not participating in, doh!12:48
@fungicide:matrix.orgyes, if i can't find them, clearing the unread count doesn't make the dot go away12:53
@harbott.osism.tech:regio.chatoh, I found something: at the top left of the "thread" window, there's a circled "<". clicking on that changes the view to a list of all threads (or so I assume). after going through all four of them, the room is marked all read now. incidentally my biggest issue with slack is that I don't get notified about threads that happen without my involvement, so I often miss to read them, thus I cannot even complain that this has been done this way here17:56
@fungicide:matrix.orgi found the same, but so many threads and clicking through most of them didn't fully solve it18:02
@jim:acmegating.comzuul-maint: i think we need https://review.opendev.org/886552 to unblock changes to... well probably most zuul repos18:29
@jim:acmegating.comdepends-on from https://review.opendev.org/886432 suggest that works18:29
@fungicide:matrix.orghttps://packages.ubuntu.com/search?keywords=podman doesn't instill me with confidence that it will fix things for more than a few minutes18:46
@fungicide:matrix.orgit looks like they're copying it from jammy-updates to the jammy suite index, in which case it's only a matter of a day or so before podman=3.4.4+ds1-1ubuntu1 will be returning a "not found" error18:48
@jim:acmegating.comfungi: well, optimistically, maybe whatever version mismatch is happening now will be resolved then.  pessimistically, maybe we should switch back to docker.18:50
@fungicide:matrix.orgyeah, i went ahead and emergency approved it, just need to keep an eye on it because it will likely break again18:51
@fungicide:matrix.orgnon-amd64 updates seem to be slightly delayed, so they may keep working this way a little longer, fwiw18:52
@jim:acmegating.comif anyone has time to investigate the issue and look into a better fix, that would be welcome :)18:52
@fungicide:matrix.orgcorvus: if you have a moment to skim https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394 does that seem like it could be the same issue? (reported two days ago by gtema)18:56
@gtema:matrix.orgNot by gtema18:57
@fungicide:matrix.orgd'oh! yep sorry, that's not your account18:58
@jim:acmegating.comfungi: yes that looks like the error18:58
@gtema:matrix.orgNo problem fungi18:58
@fungicide:matrix.orgcorvus: looking at the bug report, it does seem to be a problem with the combination of things they packaged in the new version, so short of pinning to the prior version or repackaging it ourselves i'm not sure i have a better suggestion for now than to try and raise the visibility of that bug report19:24
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul-jobs] 886552: Pin podman on jammy https://review.opendev.org/c/zuul/zuul-jobs/+/88655219:27
@fungicide:matrix.orglibpod (3.4.4+ds1-1ubuntu1.22.04.1) jammy-security; urgency=medium19:28
* Add d/p/lp-2007972-play-kube-don-t-force-pull-infra-image.patch
to prevent play kube from unwanted force-pull of infra image
and with that unwanted (untrusted) k8s pause (LP: #2007972).
@fungicide:matrix.orgso that was a backported fix for https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/200797219:29
@jim:acmegating.comthe person in the bug report installed the containernetwork-plugins from kinetic to fix the problem19:30
@fungicide:matrix.orgyeah, if you read the other bug report, that's because kinetic is almost eol so the package maintainers opted not to backport the fix to it19:31
@jim:acmegating.comwell i just mean that it appears that the backported fix inadvertently requires a later version of containernetwork-plugins19:33
@fungicide:matrix.orgoh, i see19:33
@jim:acmegating.comand that the reporter fixed that by installing a later version, which happens to be the one available in kinetic19:33
@jim:acmegating.comwhat's in lunar and mantic aren't very different in version numbers, so they might work too19:33
@jim:acmegating.comfungi: should i add a comment to 2007972 saying that it may have caused 2024394?19:35
@jim:acmegating.com(ie, does that sound correct to you?)19:36
@fungicide:matrix.orghah, i was just hitting submit on that19:36
@jim:acmegating.comperfect :)19:36
@jim:acmegating.comi marked 394 as affecting me19:37
@fungicide:matrix.orgso anyway, yes we could try that as a longer term workaround19:37
@jim:acmegating.comyeah, sounds like we may have a next bad fix after the current bad fix breaks :)19:38
@fungicide:matrix.orgthere are a few ways to go about pulling in a package from a newer ubuntu version, but as a distro they differ enough from the debian package priority system i'm familiar with that i don't know whether just adding lunar to the sources list will cause it to want to upgrade everything without some very strict repository pinning. almost might be easier to download and `dpkg -i` the deb as a workaround19:39

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!