** Tags added: id-5cc08e5a2b55986e1a179d0a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on Ubuntu 19.04
To manage notifications about
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
** Changed in: snapd
Assignee: Zygmunt Krynicki (zyga) => Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on Ubuntu
The snapd part of this has landed in
https://github.com/snapcore/snapd/pull/6771 and will be part of the 2.39
upload.
** Changed in: snapd
Status: In Progress => Fix Committed
** Changed in: snapd (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification
just don't read the commit messages and you'll be fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on Ubuntu 19.04
To manage
Oh come on! Avengers Endgame comes out in 15 minutes in the UK, don't
spoil it for me mvo!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on
Yes, mvo lives in a future in which he's already implemented that
feature, whereas us mere mortals are stuck waiting for it to arrive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
On Wed, 24 Apr 2019 at 16:00, Michael Vogt wrote:
>
> I am adding a livecd-rootfs task - it would be nice if seed.yaml
> manipulation would add an extra check at the end. Ideally we should call
> a new "snap debug validate-seed " during the build process.
> livecd-rootfs already build-depends on
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Triaged
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
I am adding a livecd-rootfs task - it would be nice if seed.yaml
manipulation would add an extra check at the end. Ideally we should call
a new "snap debug validate-seed " during the build process.
livecd-rootfs already build-depends on snapd so that should be ok, yes?
The PR for this is
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted seed.yaml on Ubuntu
I looked at this a bit more and the following change broke the
installer:
https://git.launchpad.net/livecd-
rootfs/commit/?id=f4fa240ed7a43ed927634d5829812e37955d4b4c
this was uploaded to livecd-rootfs at apr-12 so it ended up on the
medium on 20190413.
The following commit fixed it:
>From what I understand the immediate crisis is over, correct? We had an
incorrect image right before the release but for the final release
things got fixed. I would love to know what exactly happend with the
image and if that was an installer or an image builder issues. I think
we need to improve
Tried once with current release mage, works ok.
So maybe it was just the image 2 day prior to release though that seems
curious..
Maybe if time permits will try release image a couple of times to see if the
issue arises.
For info sake the installer log's snapd mentions attached from 'bad'
I did a clean install with the Alpha image and did not notice any
issues, snapd did not panic, seed yaml looked correct.
However, the format of seed yaml is somewhat weird, it looks like this
(with empty line following -):
snaps:
-
name: foo
file: bar.snap
If by any chance (a bug in the
I hope it is this image only:
InstallationDate: Installed on 2019-04-17 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can't reproduce this with the released image. Any idea what scenario
it creates the broken seed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825437
Title:
snapd fails to process corrupted
** Summary changed:
- Fails to work on a fresh 19.04 install
+ snapd fails to process corrupted seed.yaml on Ubuntu 19.04
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
18 matches
Mail list logo
