SRU 0.14 tracking bug

0.13 is not yet in zesty as the autopackagetest run failed.

http://autopkgtest.ubuntu.com/packages/u/ubuntu-image/zesty/armhf

I've requested a re-run of the test as it seems like a temporary failure.

The re-run failed.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/u/ubuntu-image/20170111_171929_431b1@/log.gz

On Jan 11, 2017, at 06:31 PM, Brian Murray wrote:

>https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
>/autopkgtest-zesty/zesty/armhf/u/ubuntu-
>image/20170111_171929_431b1@/log.gz

Most likely, it's an unrelated armhf regression. See LP: #1655735

If we can't figure that out, we'll probably want to either whitelist armhf or
skip the test on that platform.

I'm going to ditch the 0.13 release. 0.14 will have some fixes for the CI problems, so we'll supersede.

Hello Barry, 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/0.14+16.04ubuntu2 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

Hello Barry, or anyone else affected,

Accepted ubuntu-image into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/0.14+16.10ubuntu2 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

Images built with both the Yakkety and Xenial versions pass the manual boot test with amd64 images.

This bug was fixed in the package ubuntu-image - 0.14+16.10ubuntu2

---------------
ubuntu-image (0.14+16.10ubuntu2) yakkety; urgency=medium

  * SRU tracking bug LP: #1655133
  * d/changelog: Clean up bug tags so as not to confuse SRU linkage.

ubuntu-image (0.14+16.10ubuntu1) yakkety; urgency=medium

  * Add CI for Python 3.6. (LP:1650402)
  * Fix the test suite for sparse files on ZFS. (LP:1656371)
  * d/t/control: Add Restriction: isolation-machine for the mount test
    since devmapper is not namespaced and thus can interfere with other
    containers. This will prevent the test from running in schroot and
    lxd/lxc backends, but will continue to run in qemu backends.
    (LP:1656391)

ubuntu-image (0.13+16.10ubuntu2) yakkety; urgency=medium

  * d/tests/mount: Fix a typo and handle a case where the root file system
    isn't found.

ubuntu-image (0.13+16.10ubuntu1) yakkety; urgency=medium

  * Refuse to write images to /tmp when running ubuntu-image as a snap,
    since the snap's /tmp is not accessible to the user. (LP:1646968)
  * When sparse copying the resulting disk image, don't try to preserve
    mode,ownership,timestamps. Over remote file systems (e.g. afp, hgfs)
    this can fail. Over local file systems, they'll be preserved anyway.
    (LP:1637554)
  * Use the `role` attribute of the gadget.yaml when creating images,
    especially for `role:mbr` and `role:system-data` (LP:1642914 and
    LP:1643086)
  * d/tests/mount: Switch to the stable channel for snaps.
  * Make the test suite immune to the locale. (LP:1638570)

 -- Barry Warsaw <email address hidden> Fri, 20 Jan 2017 09:57:13 -0500

The verification of the Stable Release Update for ubuntu-image has completed successfully and the package has now been 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.

This bug was fixed in the package ubuntu-image - 0.14+16.04ubuntu2

---------------
ubuntu-image (0.14+16.04ubuntu2) xenial; urgency=medium

  * SRU tracking bug LP: #1655133
  * d/changelog: Clean up bug tags so as not to confuse SRU linkage.

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

  * Add CI for Python 3.6. (LP:1650402)
  * Fix the test suite for sparse files on ZFS. (LP:1656371)
  * d/t/control: Add Restriction: isolation-machine for the mount test
    since devmapper is not namespaced and thus can interfere with other
    containers. This will prevent the test from running in schroot and
    lxd/lxc backends, but will continue to run in qemu backends.
    (LP:1656391)

ubuntu-image (0.13+16.04ubuntu2) xenial; urgency=medium

  * d/tests/mount: Fix a typo and handle a case where the root file system
    isn't found.

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

  * Refuse to write images to /tmp when running ubuntu-image as a snap,
    since the snap's /tmp is not accessible to the user. (LP:1646968)
  * When sparse copying the resulting disk image, don't try to preserve
    mode,ownership,timestamps. Over remote file systems (e.g. afp, hgfs)
    this can fail. Over local file systems, they'll be preserved anyway.
    (LP:1637554)
  * Use the `role` attribute of the gadget.yaml when creating images,
    especially for `role:mbr` and `role:system-data` (LP:1642914 and
    LP:1643086)
  * d/tests/mount: Switch to the stable channel for snaps.
  * Make the test suite immune to the locale. (LP:1638570)

 -- Barry Warsaw <email address hidden> Fri, 20 Jan 2017 09:59:20 -0500