[SRU] 2.56

[Michael Vogt]

This is a new version of snapd.

The changelog is available here https://github.com/snapcore/snapd/blob/2.56/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.56 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits).

The snappy team released a new release that we want SRU into bionc+. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests.

GitHub Actions test runs can be found at https://github.com/snapcore/snapd/actions?query=branch%3Arelease%2F2.56

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapd - 2.56+22.10

---------------
snapd (2.56+22.10) kinetic; urgency=medium

  * New upstream release, LP: #1974147
    - portal-info: Add CommonID Field
    - asserts/info,mkversion.sh: capture max assertion formats in
      snapd/info
    - tests: improve the unit testing workflow to run in parallel
    - interfaces: allow map and execute permissions for files on
      removable media
    - tests: add spread test to verify that connections are preserved if
      snap refresh fails
    - tests: Apparmor sandbox profile mocking
    - cmd/snap-fde-keymgr: support for multiple devices and
      authorizations for add/remove recovery key
    - cmd/snap-bootstrap: Listen to keyboard added after start and
      handle switch root
    - interfaces,overlord: add support for adding extra mount layouts
    - cmd/snap: replace existing code for 'snap model' to use shared
      code in clientutil (2/3)
    - interfaces: fix opengl interface on RISC-V
    - interfaces: allow access to the file locking for cryptosetup in
      the dm-crypt interface
    - interfaces: network-manager: add AppArmor rule for configuring
      bridges
    - i/b/hardware-observe.go: add access to the thermal sysfs
    - interfaces: opengl: add rules for NXP i.MX GPU drivers
    - i/b/mount_control: add an optional "/" to the mount target rule
    - snap/quota: add values for journal quotas (journal quota 2/n)
    - tests: spread test for uc20 preseeding covering snap prepare-image
    - o/snapstate: remove deadcode breaking static checks
    - secboot/keymgr: extend unit tests, add helper for identify keyslot
      used error
    - tests: use new snaps.name and snaps.cleanup tools
    - interfaces: tweak getPath() slightly and add some more tests
    - tests: update snapd testing tools
    - client/clientutil: add shared code for printing model assertions
      as yaml or json (1/3)
    - debug-tools: list all snaps
    - cmd/snap: join search terms passed in the command line
    - osutil/disks: partition UUID lookup
    - o/snapshotstate: refactor snapshot read/write logic
    - interfaces: Allow locking in block-devices
    - daemon: /v2/system-recovery-keys remove API
    - snapstate: do not auto-migrate to ~/Snap for core22 just yet
    - tests: run failed tests by default
    - o/snapshotstate: check installed snaps before running 'save' tasks
    - secboot/keymgr: remove recovery key, authorize with existing key
    - deps: bump libseccomp to include build fixes, run unit tests using
      CC=clang
    - cmd/snap-seccomp: only compare the bottom 32-bits of the flags arg
      of copy_file_range
    - osutil/disks: helper for obtaining the UUID of a partition which
      is a mount point source
    - image/preseed: umount the base snap last after writable paths
    - tests: new set of nested tests for uc22
    - tests: run failed tests on nested suite
    - interfaces: posix-mq: add new interface
    - tests/main/user-session-env: remove openSUSE-specific tweaks
    - tests: skip external backend in mem-cgroup-disabled test
    - snap/quota: change the journal quota period to be a time.Duration
    - interfaces/apparmor: allow executin...

[Łukasz Zemczak (sil2100)]

Hello Michael, or anyone else affected,

Accepted snapd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd/2.56.2+22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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 snapd (2.56.2+22.04ubuntu1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.4 (armhf)

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/jammy/update_excuses.html#snapd

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

Thank you!

[Sergio Cazzolato (sergio-j-cazzolato)]

Ran the spread tests and these are the results https://paste.ubuntu.com/p/jHbKG4XDw8/

I see the tests uc20-create-partitions failing, still need to research this error.

Manual tests and checks passed.

[Łukasz Zemczak (sil2100)]

Fingers crossed that it's not some actual failure! Please give us a sign if we can proceed with the release of the package. I'd like it in -updates ASAP because we need to respin 22.04.1 images ASAP as well. Thank you!

[Alberto Mardegan (mardy)]

This is not an actual failure, but an error in the tests: the commit 5870a0aa6fd2e39b4f059efb50b443c3423edda9 [1] needs to be cherry-picked into the 2.56 branch in order to fix the test.

I don't know if this is necessary though, or if we can promote the package even if the test is failing.

[1]: https://github.com/snapcore/snapd/commit/5870a0aa6fd2e39b4f059efb50b443c3423edda9

[Łukasz Zemczak (sil2100)]

I have discussed this issue with Alberto and he does not think that the wrong test-case could be hiding a potential bug. In this case, seeing that all other tests are green, I'll mark this as verification-done. Normally I'd wait for a formal +1 from Sergio, but having this in -updates is time-critical for the point release. Some other reasoning:
 * Sergio already ran manual tests and manual checks, all passing
 * snapd 2.56.2 was already available as a snap since longer, and used on user machines due to the reexec logic

With all this in mind, let's proceed with getting this released.

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapd - 2.56.2+22.04ubuntu1

---------------
snapd (2.56.2+22.04ubuntu1) jammy; urgency=medium

  * Cherry pick https://github.com/snapcore/snapd/pull/12011
    to fix launching snaps OEM install (LP: #1983528)

snapd (2.56.2+22.04) jammy; urgency=medium

  * New upstream release, LP: #1974147
    - o/snapstate: exclude services from refresh app awareness hard
      running check
    - cmd/snap: support custom apparmor features dir with snap
      prepare-image

 -- Michael Vogt <email address hidden> Mon, 08 Aug 2022 11:17:19 +0200

[Łukasz Zemczak (sil2100)]

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