On Thu, Dec 13, 2018 at 03:50:51AM -0000, Mark Eichin wrote: > Not sure if this should get a new ticket, but if `snap debug > connectivity` fails, the whole upgrade mysteriously aborts (user sees > ```Reading state information... Done > > Restoring original system state > > Aborting > ``` and `main.log` shows ```2018-12-12 21:24:20,067 DEBUG running > Quirks.bionicPostInitialUpdate > 2018-12-12 21:24:20,367 DEBUG abort called > ``` with literally no other output anywhere. > > `strace` is what finds the `snap debug connectivity` call, and `service > snapd status` shows `Active: failed (Result: start-limit-hit)` - > `service snapd start` fixes that and `do-release-upgrade` goes through > fine. > > (It's not just me, https://askubuntu.com/questions/1078692/cant-upgrade- > ubuntu-16-04-to-18-04-lts/1100514 looks to be the same symptoms, but it > wasn't until I'd figured out that `snap` was involved that I found this > feature-ticket; I don't think it's widely known, I believe most users > don't even know snap is *in* 16.04, and certainly won't notice `snapd` > being broken without other hints...)
Could you please open a new bug report about the issue you've encountered using 'ubuntu-bug ubuntu-release-upgrader-core'? That'll include log files which might help. Thanks! -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780841 Title: ubuntu-release-upgrader should transition debs to snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
