SRU 1.9 tracking bug

[Łukasz Zemczak]

New SRU tracking bug (with exception) for ubuntu-image 1.9 in Eoan, Bionic and Xenial.

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

[Impact]

ubuntu-image 1.9 fixes some bugs and pays down some technical debt. This release features basic .disk/info support and changes the behavior of no longer removing /boot/grub contents for classic builds.

[Test Case]

Create an image using the official 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.

Optionally, a uc20 model-assertion ubuntu-core build could be performed as part of the validation.

[Regression Potential]

* ubuntu-image may not produce a bootable image

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

[Brian Murray (brian-murray)]

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.9+19.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 and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. 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.

[Brian Murray (brian-murray)]

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.9+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 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.

[Brian Murray (brian-murray)]

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.9+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 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.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

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

livecd-rootfs/2.408.57 (i386)

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/xenial/update_excuses.html#ubuntu-image

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

Thank you!

[Łukasz Zemczak (sil2100)]

Verified 1.9+19.10ubuntu1 on an eoan multipass instance - was able to build bootable core and classic images successfully.

[Łukasz Zemczak (sil2100)]

Verified 1.9+18.04ubuntu1 on a bionic multipass instance - was able to build bootable core and classic images successfully as well. Moving on!

[Łukasz Zemczak (sil2100)]

Verified 1.9+16.04ubuntu1 on a xenial multipass instance. Was able to build a bootable core image. As for classic, we still have the livecd-rootfs issue there, so the image didn't build out-of-the-box without tweaking. But as before, this is not a regression caused by u-i.

[Łukasz Zemczak (sil2100)]

I have also test built an uc20 image using ubuntu-image 1.9+18.04ubuntu1 on bionic. I was able to build it successfully, though it was not booting. I have poked the snapd team about it. The image boots up and displays the grub menu, but all the entries are printing out errors and not proceeding. Doesn't seem like it's related to the ubuntu-image SRU though, as the image seems to have been created correctly.

Anyway, not something that should be blocking this SRU. Please release!

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-image - 1.9+19.10ubuntu1

---------------
ubuntu-image (1.9+19.10ubuntu1) eoan; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * Add support for populating a .disk/info file on the target image rootfs.
    (LP:1856684)
  * Design change: no longer remove /boot/grub from the rootfs for classic
    image builds. This allows developers to have more freedom on deciding how
    boot configuration should be handled. (LP:1817050)
  * Fix the autopkgtest story on focal. Only for this series, remove the py37
    tox environment as it does not work due to pyparted being 3.8-only.
  * Fix manifest generation for uc20 builds. (LP:1856205)
  * SRU tracking number LP: #1864977

  [ Maciej Borzecki ]
  * ubuntu_image: update schema validator to allow gadget update specific
    keys & little cleanups. (LP:1856903)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 29 Jan 2020 16:33:36 +0100

[Brian Murray (brian-murray)]

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.

[Launchpad Janitor (janitor)]

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

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

  [ Łukasz 'sil2100' Zemczak ]
  * Design change: no longer remove /boot/grub from the rootfs for classic
    image builds. This allows developers to have more freedom on deciding how
    boot configuration should be handled. (LP:1817050)
  * Fix the autopkgtest story on focal. Only for this series, remove the py37
    tox environment as it does not work due to pyparted being 3.8-only.
  * Fix manifest generation for uc20 builds. (LP:1856205)
  * SRU tracking number LP: #1864977

  [ Maciej Borzecki ]
  * ubuntu_image: update schema validator to allow gadget update specific
    keys & little cleanups. (LP:1856903)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 29 Jan 2020 16:33:36 +0100

[Launchpad Janitor (janitor)]

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

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

  [ Łukasz 'sil2100' Zemczak ]
  * Add support for populating a .disk/info file on the target image rootfs.
    (LP:1856684)
  * Design change: no longer remove /boot/grub from the rootfs for classic
    image builds. This allows developers to have more freedom on deciding how
    boot configuration should be handled. (LP:1817050)
  * Fix the autopkgtest story on focal. Only for this series, remove the py37
    tox environment as it does not work due to pyparted being 3.8-only.
  * Fix manifest generation for uc20 builds. (LP:1856205)
  * SRU tracking number LP: #1864977

  [ Maciej Borzecki ]
  * ubuntu_image: update schema validator to allow gadget update specific
    keys & little cleanups. (LP:1856903)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 29 Jan 2020 16:33:36 +0100