snapd 2.23.6 SRU tracking bug
Bug #1673568 reported by
Zygmunt Krynicki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
Undecided
|
Unassigned | ||
snapd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This release contains the following change as compared to 2.23.1 (2.23.2 was a failed build)
https:/
In cases where snapd 2.0.10 is used on a fresh install of Ubuntu, snapd will re-exec into the ubuntu-core/core snap, complete the core transition if necessary and then hit an issue where the core's configure hook fails to run.
The reason for this failure is that configure hook is executed with the help of snap-confine but 2.0.10 did not have snap-confine yet (it was still ubuntu-
As a workaround we now detect this case and merely warn (rather than fail) if a hook cannot be executed because snap-confine is not available.
summary: |
- snapd 2.23.2 SRU tracking bug + snapd 2.23.3 SRU tracking bug |
description: | updated |
summary: |
- snapd 2.23.3 SRU tracking bug + snapd 2.23.6 SRU tracking bug |
Changed in snapd (Ubuntu Yakkety): | |
status: | New → Fix Committed |
Changed in snapd (Ubuntu): | |
status: | New → Fix Released |
Changed in snapd: | |
status: | New → Fix Released |
To post a comment you must log in.
Hello Zygmunt, or anyone else affected,
Accepted snapd into yakkety-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ snapd/2. 23.6+16. 10 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/ PerformingSRUVe rification . Thank you in advance!