sru curtin 2017-06-12 - 0.1.0~bzr505-0ubuntu1

Bug #1697545 reported by Scott Moser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin (Ubuntu)
Fix Released
Medium
Unassigned
Xenial
Fix Released
Medium
Unassigned
Yakkety
Fix Released
Medium
Unassigned
Zesty
Fix Released
Medium
Unassigned
Artful
Fix Released
Medium
Unassigned

Bug Description

== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:

  * Make systems with root on bcache use root=UUID=. (LP: #1680591)
  * Fix iscsi disks that have a ':' in the target name. (LP: #1679222)
  * Add support for installing Ubuntu-Core 16 images
  * Clear and re-order UEFI boot methods during UEFI grub installation. (LP: #1680917)
  * Fix stacked storage configurations with iSCSI (LP: #1683910)
  * clear-holders: mdadm use /proc/mdstat to wait for array to stop (LP: #1682584)
  * clear-holders: make bcache handler wait for device shutdown (LP: #1680409)
  * Copy curtin install log into target. (LP: #1684128)
  * block_meta: Attempt to mount by UUID= if possible (LP: #1676991)

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/CurtinUpdates

Curtin now contains an extensive integration test suite that is ran using
the SRU package for each releases. These suite has documentation here:
https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

In order to avoid regression to existing MAAS product, the MAAS team will
run their continuous integration test against the curtin that is in
-proposed. A successful run will be required before the proposed curtin
can be let into -updates.

The curtin team will be in charge of attaching the artifacts and console
output of the appropriate run to the bug. Curtin team members will not
mark ‘verification-done’ until this has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.

<TODO: attach curtin-proposed test artifacts from vmtest for every SRU release, not a link as links expire>
<TODO: attach maas-proposed test artifacts from vmtest for every SRU release, not a link as links expire>

[Discussion]
The primary features / fixes needed here are for Ubuntu Core support.

== End SRU Template ==

[Below here are for 16.04, 16.10 and 17.04]
  - vmtest: let the socket level select a port rather than us picking one.
  - Fix deb build by mocking call to udevadm settle
  - Clear and re-order UEFI boot methods during UEFI grub installation.
  - Resolve bcache race-conditions
  - tests: clean up usage of collect files
  - Allow re-use of vmtest output
  - Fix stacked storage configurations with iSCSI (LP: #1683910)
  - vmtests: enable tests to apply storage config to validate clear_holders path
  - mdadm_stop: Add retry and additional steps to halt a resync
  - vmtests: Add Artful release and update classes
  - clear-holders: mdadm use /proc/mdstat to wait for array to stop (LP: #1682584)
  - uc16 curthooks: add 'network' key to config file (LP: #1685000)
  - Doc and makefile updates for build and test on new systems.
  - clear-holders: make bcache handler wait for device shutdown (LP: #1680409)
  - vmtest: Use utf-8 and fix pseudo test collect_output
  - vmtest: fix path to install log, and utilize the globally copied paths.
  - Copy curtin install log into target. (LP: #1684128)
  - vmtest: add in post-test log post-processing
  - vmtest: update source.list test
  - add recursive flag to do_umount, add --umount to block-meta
  - load_command_environment: fix strict flag, and unit tests.
  - block_meta: Attempt to mount by UUID= if possible (LP: #1676991)

[Below here are for 16.04 and 16.10 only, as already included in 17.04]
  - Make systems with root on bcache use root=UUID=. (LP: #1680591)
  - Fix iscsi disks that have a ':' in the target name. (LP: #1679222)
  - tests: re-enable ZestyTestMdadmBcache.
  - curthooks: fix pylint reported error when using ubuntu_core_curthooks.
  - Add support for installing Ubuntu-Core 16 images
  - Add 'STORAGE_CONFIG_V1_DD' to the feature list.
  - flake8: fix flake8 issues with previous merge.
  - Support selection of target disk for dd images install via storage config. (LP: #1640301)
  - vmtest: have vmtest-sync-images avoid running when jenkins-runner is.
  - tools/curtin-from-container: do not use lxc file push --create-dirs
  - tests: enable curtainer to pull down curtin source locally
  - tests: make nose output always include class name and method.
  - tools/curtin-from-container: default to verbosity level 0, not 2.

Scott Moser (smoser)
Changed in curtin (Ubuntu Xenial):
status: New → Confirmed
Changed in curtin (Ubuntu Yakkety):
status: New → Confirmed
Changed in curtin (Ubuntu Zesty):
status: New → Confirmed
Changed in curtin (Ubuntu Artful):
status: New → Fix Released
Changed in curtin (Ubuntu Xenial):
importance: Undecided → Medium
Changed in curtin (Ubuntu Yakkety):
importance: Undecided → Medium
Changed in curtin (Ubuntu Zesty):
importance: Undecided → Medium
Changed in curtin (Ubuntu Artful):
importance: Undecided → Medium
Scott Moser (smoser)
description: updated
description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Scott, or anyone else affected,

Accepted curtin into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr505-0ubuntu1~17.04.1 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!

Changed in curtin (Ubuntu Zesty):
status: Confirmed → Fix Committed
tags: added: verification-needed
Changed in curtin (Ubuntu Yakkety):
status: Confirmed → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Scott, or anyone else affected,

Accepted curtin into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr505-0ubuntu1~16.10.1 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!

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Scott, or anyone else affected,

Accepted curtin into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr505-0ubuntu1~16.04.1 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!

Changed in curtin (Ubuntu Xenial):
status: Confirmed → Fix Committed
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :
Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Change of SRU verification policy

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

tags: added: verification-done
removed: verification-needed
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We have tested and confirm it works as expected. Partial MAAS CI logs for xenial can be seen here [1]. Zesty and Yakkety were tested manually.

[1]: http://pastebin.ubuntu.com/24964664/

tags: added: verification-done-xenial verification-done-yakkety verification-done-zesty
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Reminder of SRU verification policy change

Thank you for taking the time to verify this stable release fix. We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE). Please remove the verification-done tag and add one for the release you have tested the package in. Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

This bug was fixed in the package curtin - 0.1.0~bzr505-0ubuntu1~16.10.1

---------------
curtin (0.1.0~bzr505-0ubuntu1~16.10.1) yakkety-proposed; urgency=medium

  * New upstream snapshot. (LP: #1697545)
    - vmtest: let the socket level select a port rather than us picking one.
    - Fix deb build by mocking call to udevadm settle
    - Clear and re-order UEFI boot methods during UEFI grub installation.
    - Resolve bcache race-conditions
    - tests: clean up usage of collect files
    - Allow re-use of vmtest output
    - Fix stacked storage configurations with iSCSI
    - vmtests: enable tests to apply storage config to validate clear_holders
      path
    - mdadm_stop: Add retry and additional steps to halt a resync
    - vmtests: Add Artful release and update classes
    - clear-holders: mdadm use /proc/mdstat to wait for array to stop
    - uc16 curthooks: add 'network' key to config file
    - Doc and makefile updates for build and test on new systems.
    - clear-holders: make bcache handler wait for device shutdown
    - vmtest: Use utf-8 and fix pseudo test collect_output
    - vmtest: fix path to install log, and utilize the globally copied paths.
    - Copy curtin install log into target.
    - vmtest: add in post-test log post-processing
    - vmtest: update source.list test
    - add recursive flag to do_umount, add --umount to block-meta
    - load_command_environment: fix strict flag, and unit tests.
    - block_meta: Attempt to mount by UUID= if possible
    - Make systems with root on bcache use root=UUID=.
    - Fix iscsi disks that have a ':' in the target name.
    - tests: re-enable ZestyTestMdadmBcache.
    - curthooks: fix pylint reported error when using ubuntu_core_curthooks.
    - Add support for installing Ubuntu-Core 16 images
    - Add 'STORAGE_CONFIG_V1_DD' to the feature list.
    - flake8: fix flake8 issues with previous merge.
    - Support selection of target disk for dd images install via storage
      config.
    - vmtest: have vmtest-sync-images avoid running when jenkins-runner is.
    - tools/curtin-from-container: do not use lxc file push --create-dirs
    - tests: enable curtainer to pull down curtin source locally
    - tests: make nose output always include class name and method.
    - tools/curtin-from-container: default to verbosity level 0, not 2.

 -- Scott Moser <email address hidden> Mon, 12 Jun 2017 16:31:10 -0400

Changed in curtin (Ubuntu Yakkety):
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 curtin 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.

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

This bug was fixed in the package curtin - 0.1.0~bzr505-0ubuntu1~17.04.1

---------------
curtin (0.1.0~bzr505-0ubuntu1~17.04.1) zesty; urgency=medium

  * New upstream snapshot. (LP: #1697545)
    - vmtest: let the socket level select a port rather than us picking one.
    - Fix deb build by mocking call to udevadm settle
    - Clear and re-order UEFI boot methods during UEFI grub installation.
    - Resolve bcache race-conditions
    - tests: clean up usage of collect files
    - Allow re-use of vmtest output
    - Fix stacked storage configurations with iSCSI
    - vmtests: enable tests to apply storage config to validate clear_holders
      path
    - mdadm_stop: Add retry and additional steps to halt a resync
    - vmtests: Add Artful release and update classes
    - clear-holders: mdadm use /proc/mdstat to wait for array to stop
    - uc16 curthooks: add 'network' key to config file
    - Doc and makefile updates for build and test on new systems.
    - clear-holders: make bcache handler wait for device shutdown
    - vmtest: Use utf-8 and fix pseudo test collect_output
    - vmtest: fix path to install log, and utilize the globally copied paths.
    - Copy curtin install log into target.
    - vmtest: add in post-test log post-processing
    - vmtest: update source.list test
    - add recursive flag to do_umount, add --umount to block-meta
    - load_command_environment: fix strict flag, and unit tests.
    - block_meta: Attempt to mount by UUID= if possible
    - Make systems with root on bcache use root=UUID=.

 -- Scott Moser <email address hidden> Mon, 12 Jun 2017 15:57:40 -0400

Changed in curtin (Ubuntu Zesty):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package curtin - 0.1.0~bzr505-0ubuntu1~16.04.1

---------------
curtin (0.1.0~bzr505-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/new-upstream-snapshot: create tarball in .. otherwise it
    will get deleted in the cleaning of files.
  * New upstream snapshot. (LP: #1697545)
    - vmtest: let the socket level select a port rather than us picking one.
    - Fix deb build by mocking call to udevadm settle
    - Clear and re-order UEFI boot methods during UEFI grub installation.
    - Resolve bcache race-conditions
    - tests: clean up usage of collect files
    - Allow re-use of vmtest output
    - Fix stacked storage configurations with iSCSI
    - vmtests: enable tests to apply storage config to validate clear_holders
      path
    - mdadm_stop: Add retry and additional steps to halt a resync
    - vmtests: Add Artful release and update classes
    - clear-holders: mdadm use /proc/mdstat to wait for array to stop
    - uc16 curthooks: add 'network' key to config file
    - Doc and makefile updates for build and test on new systems.
    - clear-holders: make bcache handler wait for device shutdown
    - vmtest: Use utf-8 and fix pseudo test collect_output
    - vmtest: fix path to install log, and utilize the globally copied paths.
    - Copy curtin install log into target.
    - vmtest: add in post-test log post-processing
    - vmtest: update source.list test
    - add recursive flag to do_umount, add --umount to block-meta
    - load_command_environment: fix strict flag, and unit tests.
    - block_meta: Attempt to mount by UUID= if possible
    - Make systems with root on bcache use root=UUID=.
    - Fix iscsi disks that have a ':' in the target name.
    - tests: re-enable ZestyTestMdadmBcache.
    - curthooks: fix pylint reported error when using ubuntu_core_curthooks.
    - Add support for installing Ubuntu-Core 16 images
    - Add 'STORAGE_CONFIG_V1_DD' to the feature list.
    - flake8: fix flake8 issues with previous merge.
    - Support selection of target disk for dd images install via storage
      config.
    - vmtest: have vmtest-sync-images avoid running when jenkins-runner is.
    - tools/curtin-from-container: do not use lxc file push --create-dirs
    - tests: enable curtainer to pull down curtin source locally
    - tests: make nose output always include class name and method.
    - tools/curtin-from-container: default to verbosity level 0, not 2.

 -- Scott Moser <email address hidden> Mon, 12 Jun 2017 16:39:14 -0400

Changed in curtin (Ubuntu Xenial):
status: Fix Committed → Fix Released
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.