Activity log for bug #2049373

Date Who What changed Old value New value Message
2024-01-15 10:38:06 Łukasz Zemczak bug added bug
2024-01-15 10:38:11 Łukasz Zemczak nominated for series Ubuntu Jammy
2024-01-15 10:38:11 Łukasz Zemczak bug task added livecd-rootfs (Ubuntu Jammy)
2024-01-15 10:38:16 Łukasz Zemczak livecd-rootfs (Ubuntu): status Triaged Invalid
2024-01-15 10:38:19 Łukasz Zemczak livecd-rootfs (Ubuntu Jammy): status New In Progress
2024-01-15 10:38:21 Łukasz Zemczak livecd-rootfs (Ubuntu Jammy): assignee Łukasz Zemczak (sil2100)
2024-01-15 10:38:22 Łukasz Zemczak livecd-rootfs (Ubuntu Jammy): importance Undecided Critical
2024-01-15 10:38:27 Łukasz Zemczak livecd-rootfs (Ubuntu Jammy): milestone ubuntu-22.04.4
2024-01-16 18:11:48 Michael Kelly bug added subscriber Michael Kelly
2024-01-16 18:12:03 Michael Kelly removed subscriber Michael Kelly
2024-01-17 12:58:19 Łukasz Zemczak description [Impact] We did not have new preinstalled raspi jammy images since many months, mostly due to the `classic` branch of the pi gadget changing to the new ubuntu-image 3.x features. This is a critical bug. The proposed, safest way forward is to create a reverted, ubuntu-image 2.x targeted gadget branch and make sure that livecd-rootfs uses that one instead. [Test Case] TBD [Regression Potential] There should be none per-se, as currently no raspi builds are succeeding. That being said, the images need to be checked if no essential gadget changes have been missed, seeing if the resulting new raspi jammy images work as intended. At the same time, there is small risk that other, non-raspi images will suddenly fail to build. [Impact] We did not have new preinstalled raspi jammy images since many months, mostly due to the `classic` branch of the pi gadget changing to the new ubuntu-image 3.x features. This is a critical bug. The proposed, safest way forward is to create a reverted, ubuntu-image 2.x targeted gadget branch and make sure that livecd-rootfs uses that one instead. [Test Case] After accepting the package to -proposed, run a test build of arm64 and armhf raspi daily-preinstalled images. Those should now succeed. Download the image and do a boot test + perform a few basic smoke tests. [Regression Potential] There should be none per-se, as currently no raspi builds are succeeding. That being said, the images need to be checked if no essential gadget changes have been missed, seeing if the resulting new raspi jammy images work as intended. In theory this change might break other, non-raspi preinstalled image builds - but considering that in jammy ubuntu-image is only used to build Pi images, there's no real regression potential.
2024-01-17 19:42:54 Brian Murray livecd-rootfs (Ubuntu Jammy): status In Progress Fix Committed
2024-01-17 19:42:55 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2024-01-17 19:43:02 Brian Murray bug added subscriber SRU Verification
2024-01-17 19:43:05 Brian Murray tags verification-needed verification-needed-jammy
2024-01-19 15:44:26 Ubuntu Archive Robot bug added subscriber Utkarsh Gupta
2024-01-22 09:56:16 Łukasz Zemczak tags verification-needed verification-needed-jammy verification-done verification-done-jammy
2024-01-22 09:56:45 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2024-01-22 09:56:44 Launchpad Janitor livecd-rootfs (Ubuntu Jammy): status Fix Committed Fix Released