[Bug 1828500] Re: snapd fails always in Optimised Ubuntu Desktop images available in Microsoft Hyper-V gallery
Andy Whitcroft
apw at canonical.com
Tue Jul 16 15:33:10 UTC 2019
Hello Peter, or anyone else affected,
Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.28 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.
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-bionic
** Changed in: livecd-rootfs (Ubuntu Disco)
Status: New => Fix Committed
** Tags added: verification-needed-disco
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1828500
Title:
snapd fails always in Optimised Ubuntu Desktop images available in
Microsoft Hyper-V gallery
Status in livecd-rootfs package in Ubuntu:
Confirmed
Status in livecd-rootfs source package in Bionic:
Fix Committed
Status in livecd-rootfs source package in Disco:
Fix Committed
Bug description:
[Impact]
* Failing to do error checks on `snap-tool info` calls while
determining the bases of snaps can lead to inconsistently-seeded
images as reported in the original bug report below.
* This affects all stable releases which use automatic detection of
the base snap during image builds.
* The changes proposed introduce extra error checking which should
result in a build error, if the `snap-tool info` call fails, thus
preventing distribution of a broken image.
[Test Case]
* It may be tricky to reproduce the exact error on demand. But it
should be clear by looking at the code path in
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-
rootfs/+merge/370096
that the scenario described below may arise.
* A way to test that the changes have no *negative* impact on
functionality is to run a script such as
https://pastebin.ubuntu.com/p/wQknctr6ys/
and compare it against the expected result
https://pastebin.ubuntu.com/p/N8PXRJJV9b/
(In this case both core and core18 should have been seeded.) and
[Regression Potential]
* The regression potential for these changes is low, as they only add
extra error checking but do not change the existing logic.
--- Original Bug Report ---
Alway fails in both 18.04.2 and 19.04
Reporting the bug failed too yesterday.
As a consequence LivePatch and everything else fails that is based on snapd.
This makes system unusable. This is a supported configuration.
https://blog.ubuntu.com/2018/09/17/optimised-ubuntu-desktop-images-available-in-microsoft-hyper-v-gallery
https://blog.ubuntu.com/2019/05/07/19-04-disco-dingo-now-available-as-optimised-desktop-image-for-hyper-v
xx at xenial-Virtual-Machine:~$ sudo snap install vscode
[sudo] password for peterg:
error: too early for operation, device not yet seeded or device model not acknowledged
xx at xenial-Virtual-Machine:~$ journalctl -b -u snapd --full --no-pager
-- Logs begin at Thu 2019-05-09 20:06:58 AEST, end at Fri 2019-05-10 13:20:46 AEST. --
May 10 13:19:59 xenial-Virtual-Machine systemd[1]: Starting Snappy daemon...
May 10 13:20:00 xenial-Virtual-Machine snapd[566]: AppArmor status: apparmor is enabled and all features are available
May 10 13:20:00 xenial-Virtual-Machine snapd[566]: helpers.go:717: cannot retrieve info for snap "gnome-calculator": cannot find installed snap "gnome-calculator" at revision 352: missing file /snap/gnome-calculator/352/meta/snap.yaml
May 10 13:20:00 xenial-Virtual-Machine snapd[566]: daemon.go:379: started snapd/2.38+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-48-generic.
May 10 13:20:00 xenial-Virtual-Machine systemd[1]: Started Snappy daemon.
May 10 13:20:46 xenial-Virtual-Machine snapd[566]: api.go:1071: Installing snap "vscode" revision unset
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: snapd 2.38+18.04
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 10 13:21:25 2019
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1828500/+subscriptions
More information about the Ubuntu-sponsors
mailing list