Build the core18 pi generic image

Bug #1861520 reported by Łukasz Zemczak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
livecd-rootfs (Ubuntu)
Invalid
Critical
Łukasz Zemczak
Bionic
Fix Released
Critical
Łukasz Zemczak

Bug Description

[Impact]

Currently for uc18 we build separate images per Pi flavor, e.g. pi3, pi2, cm3. Those images are all basically identical, using one gadget and one kernel, just different assertions. With 18.04.4 we'll be switching to just building two flavors - a pi generic armhf and arm64 image.

[Test Case]

Run a cdimage -proposed beta-channel build of raspi3 arm64 and armhf images, make sure images are successfully booted and the right model-assertions are used.

To make sure there are no regressions: build a classic armhf and arm64 raspi3 image via cdimage with -proposed enabled and make sure that builds correctly as well.

[Regression Potential]

The only possible regressions might be related to image build failures.

Changed in livecd-rootfs (Ubuntu Bionic):
status: New → In Progress
importance: Undecided → Critical
Changed in livecd-rootfs (Ubuntu):
status: In Progress → Invalid
Changed in livecd-rootfs (Ubuntu Bionic):
assignee: nobody → Łukasz Zemczak (sil2100)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Łukasz, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.40 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in livecd-rootfs (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Since this change only affects ubuntu-image based builds (no other code-path altered), the regression potential is really low. So all the classic images built fine, so no regression here. As for the actual bugfix, I have ran a proposed-enabled bionic core image build on cdimage - all images besides armhf+raspi3 and arm64+raspi3 built successfully. Those that failed, failed as expected - checking the build logs, the right pi model assertion was used. Failure was because of a missing gadget in the required channel, but that is to be expected (still no valid gadget there).

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 2.525.40

---------------
livecd-rootfs (2.525.40) bionic; urgency=medium

  * Stop building per-pi-flavor images and only build a pi generic image for
    core18. (LP: #1861520)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Fri, 31 Jan 2020 16:57:01 +0100

Changed in livecd-rootfs (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.