Items last updated on 2026-04-13 (Monday). Date range identified as: “Tuesday triage”
Bugs
Many old bugs were touched by a kernel team bot (prod-kernel-team-janitor). In
most of those, the server team related task was in a closed state. I am not
mentioning those bugs here. However, the ones below are still open for us and
were all auto-closed by that kernel bot. At a first glance, it does seem that
closing them were false positives from the bot heuristics. But I am unsure if
just re-opening them without coordination with the kernel team will do much
here since they will probably just be closed again.
- https://pad.lv/1536280
- https://pad.lv/1782207
- https://pad.lv/1782208
- https://pad.lv/1808412
- https://pad.lv/1815588
https://pad.lv/2141533 | walinuxagent | [SRU] Upgrade to v2.15.0.1 on Resolute (26.04) / Q / N / J |
Miriam is no longer with Canonical. I wonder if CPC is aware of this one to e
nsure we do have someone to verify this SRU.
https://pad.lv/2148220 | libvirt | Concurrent blockcommit causes apparmor denials for layer ab… |
This was forked from LP: #2126574. While this needs a review (@hectorcao), I
asked the reporter to remove the duplications from those bugs.
Bugs not touched in 60 days:
https://pad.lv/2141692 | virglrenderer | Enable VirGL video acceleration in Ubuntu virglrenderer bui… |
This seems to be a valid request. The question is whether there is still time
for this or if we want to leave it for 26.10. I added a server-triage-discuss
tag to it.
https://pad.lv/2141694 | qemu | Add opt-in support to enable VIRGL_RENDERER_USE_VIDEO for v… |
qemu countaer part for the bug above. Also added to server-triage-discuss.
Discourse
Nothing worth mentioning here
Documentation
Nothing worth mentioning here
Migration
netplan.io blocking openvswitch (3.7.0-1build1 to 3.7.1-1) for 6 days
These were tmpfail failures a few days ago. I re-triggered all offending tests.