[FFe] SRU 1.11 tracking bug

Bug #1920955 reported by Łukasz Zemczak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Image
Critical
Łukasz Zemczak
ubuntu-image (Ubuntu)
Medium
Unassigned
Xenial
Low
Unassigned
Bionic
Low
Unassigned
Focal
Critical
Unassigned
Groovy
Low
Unassigned

Bug Description

New SRU tracking bug (with exception) for ubuntu-image 1.10 in Groovy, Focal, Bionic and Xenial + FFe for hirsute.

See https://wiki.ubuntu.com/UbuntuImageUpdates

[Impact]

ubuntu-image 1.11 is a very very very small and minor release. Basically the only real change (and feature) is related to UC20 images, and is:
 * Use "resolved-content" directory provided by newer versions of "snap prepare-image".

This is a 'safe' change, as it is fairly isolated, only doing something new when snap prepare-image supports it.

Additionally, for all series below groovy, this release also includes a bugfix for:
 * Add a workaround for mkfs.ext4 forcefully sparsifying our classic image swapfile

This is a critical change to enable proper building of new DTB-model images.

[FFe rationale]

This lands so late because all the DTB changes in snapd landed late. And we need to have these changes in the Ubuntu archive (most importantly in focal) because our UC20 image builds are using ubuntu-image from the deb (not the snap). Without this, the UC20 images that we build will not include the new DTB structure, which enables proper DTB handling via the kernel (not the gadget, as done previously).

The plus side is that this is really basically the only change in 1.11. I wouldn't even do a release if not for the fact that we want to have proper images building for focal.

[Test Case]

 * Create an image using the official uc18 amd64 model assertion. Ensure that the resulting image boots to 'press enter to configure' phase.

 * Create an ubuntu-cpc project classic image using a modified amd64 gadget tree [1] and make sure it boots.

 * Create an image using the official uc20 amd64 model assertion. Ensure that the resulting image boots (possible to ping the certification team for help).

[Regression Potential]

 * ubuntu-image may not produce a bootable image

[1] For example: https://github.com/sil2100/pc-amd64-gadget

Changed in ubuntu-image:
milestone: none → 1.11
Revision history for this message
Iain Lane (laney) wrote :

Ack, it sounds isolated and safe enough, but watch out for bugs of course.

Changed in ubuntu-image (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Note for SRU team members: the groovy upload has a slightly different changelog entry 'style' than all the others - it still includes all the required info but different than the other series. It was my mistake when creating the release, but unwinding this is a bit troublesome. So since it's stylistic only, let's just go with it! Especially that groovy will go EOL soon anyway!

Changed in ubuntu-image (Ubuntu):
status: Triaged → In Progress
Changed in ubuntu-image (Ubuntu Xenial):
status: New → In Progress
Changed in ubuntu-image (Ubuntu Bionic):
status: New → In Progress
Changed in ubuntu-image (Ubuntu Groovy):
status: New → In Progress
Changed in ubuntu-image (Ubuntu Focal):
status: New → In Progress
importance: Undecided → Critical
Changed in ubuntu-image (Ubuntu Bionic):
importance: Undecided → Low
Changed in ubuntu-image (Ubuntu Groovy):
importance: Undecided → Low
Changed in ubuntu-image (Ubuntu Xenial):
importance: Undecided → Low
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.11+20.10ubuntu1 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, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. 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 ubuntu-image (Ubuntu Groovy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-groovy
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.11+20.04ubuntu1 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 ubuntu-image (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.11+18.04ubuntu1 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, what testing has been performed on the package 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 ubuntu-image (Ubuntu Bionic):
status: In Progress → Fix Committed
tags: added: verification-needed-bionic
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.11+16.04ubuntu1 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, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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 ubuntu-image (Ubuntu):
status: In Progress → Fix Released
Changed in ubuntu-image (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed-xenial
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-image/1.11+20.04ubuntu1)

All autopkgtests for the newly accepted ubuntu-image (1.11+20.04ubuntu1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.11+20.04ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#ubuntu-image

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Changed in ubuntu-image:
status: New → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Ok, tested groovy ubuntu-image 1.11+20.10ubuntu1, successfully built a UC18 amd64 image, a UC20 amd64 image (stable channel) and a UC20 pi arm64 image. Tested that the amd64 image boots correctly.
Also built a classic bionic amd64 image (since that's what I had available from the gadget POV) and it booted fine as well.

Considering this verified.

tags: added: verification-done-groovy
removed: verification-needed-groovy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Tested focal ubuntu-image 1.11+20.04ubuntu1, successfully built a UC18 amd64 image, a UC20 amd64 image (stable channel) and a UC20 pi arm64 image. Tested that the amd64 image boots correctly.
Also built a classic bionic amd64 image as well - all good.

Considering this verified for focal as well.

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Tested bionic ubuntu-image 1.11+18.04ubuntu1, successfully built a UC18 amd64 image, a UC20 amd64 image (stable channel) and a UC20 pi arm64 image. The amd64 image seemed to work correctly.
Built a classic bionic image too and that seemed to work.

Considering this verified for bionic.

tags: added: verification-done-bionic
removed: verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Tested xenial ubuntu-image 1.11+16.04ubuntu1 and successfully built UC18 amd64, UC20 amd64 and UC20 pi arm64 images. Classic has a bit of a problem in xenial, unrelated to ubuntu-image.
Anyway, xenial is as good as it gets!

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

This bug was fixed in the package ubuntu-image - 1.11+20.10ubuntu1

---------------
ubuntu-image (1.11+20.10ubuntu1) groovy; urgency=medium

  [ Michael Vogt ]
  * Use "resolved-content" directory provided by newer versions
    of "snap prepare-image". (LP:1636927)
  * SRU tracking number LP: #1920955

 -- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 25 Mar 2021 14:55:14 +0100

Changed in ubuntu-image (Ubuntu Groovy):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for ubuntu-image 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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-image - 1.11+20.04ubuntu1

---------------
ubuntu-image (1.11+20.04ubuntu1) focal; urgency=medium

  [ Michael Vogt ]
  * Use "resolved-content" directory provided by newer versions
    of "snap prepare-image". (LP:1636927)

  [ Brian Murray ]
  * Fix a typo in README.rst.

  [ Łukasz 'sil2100' Zemczak ]
  * Add a workaround for mkfs.ext4 forcefully sparsifying our classic image
    swapfile (LP:1900718)
  * Add python3.9 to the test envlists.
  * Minor README fixups and additions, minor test-related compatibility
    changes.

  [ Sebastien Bacher ]
  * setup.py:
    - get the version in a way which is compatible with the current
      python-debian
  * SRU tracking number LP: #1920955

 -- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 25 Mar 2021 14:55:14 +0100

Changed in ubuntu-image (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-image - 1.11+18.04ubuntu1

---------------
ubuntu-image (1.11+18.04ubuntu1) bionic; urgency=medium

  [ Michael Vogt ]
  * Use "resolved-content" directory provided by newer versions
    of "snap prepare-image". (LP:1636927)

  [ Brian Murray ]
  * Fix a typo in README.rst.

  [ Łukasz 'sil2100' Zemczak ]
  * Add a workaround for mkfs.ext4 forcefully sparsifying our classic image
    swapfile (LP:1900718)
  * Add python3.9 to the test envlists.
  * Minor README fixups and additions, minor test-related compatibility
    changes.

  [ Sebastien Bacher ]
  * setup.py:
    - get the version in a way which is compatible with the current
      python-debian
  * SRU tracking number LP: #1920955

 -- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 25 Mar 2021 14:55:14 +0100

Changed in ubuntu-image (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-image - 1.11+16.04ubuntu1

---------------
ubuntu-image (1.11+16.04ubuntu1) xenial; urgency=medium

  [ Michael Vogt ]
  * Use "resolved-content" directory provided by newer versions
    of "snap prepare-image". (LP:1636927)

  [ Brian Murray ]
  * Fix a typo in README.rst.

  [ Łukasz 'sil2100' Zemczak ]
  * Add a workaround for mkfs.ext4 forcefully sparsifying our classic image
    swapfile (LP:1900718)
  * Add python3.9 to the test envlists.
  * Minor README fixups and additions, minor test-related compatibility
    changes.

  [ Sebastien Bacher ]
   * setup.py:
    - get the version in a way which is compatible with the current
      python-debian
  * SRU tracking number LP: #1920955

 -- Łukasz 'sil2100' Zemczak <email address hidden> Thu, 25 Mar 2021 14:55:14 +0100

Changed in ubuntu-image (Ubuntu Xenial):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers