[Bug 1810565] Re: Ubuntu 16.04 to Ubuntu18.04 upgrade fails on snap debug connectivity without logging any useful logs

[Brian Murray]

On Tue, Jan 08, 2019 at 06:02:42PM -0000, sergiiF wrote:
> I didn't go deep enough do understand what _checkStoreConnectivity was
> called for. It might happen that was just a part of updates validation.
> 
> I'd like to make it clear - I do understand that having snap version old
> is my fault. The ticket I created is against the logging that doesn't
> allow to figure out what is going wrong.

I understand that and what you are looking for, but I'm also concerned
about there being another bug in that the upgrader allowed you to
upgrade without having the latest version of snap installed. Could you
answer my original question regarding which release from which you were
upgrading? It'd also help to know the version of the release upgrader
you used - you can find that in /var/log/dist-upgrade/main.log.

Thanks!

--
Brian Murray

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1810565

Title:
  Ubuntu 16.04 to Ubuntu18.04 upgrade fails on snap debug connectivity
  without  logging any useful logs

Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  While running the do-release-upgrade I faced the issue. The output from log is like:
  DEBUG quirks: running bionicPostInitialUpdate
  DEBUG running Quirks.bionicPostInitialUpdate
  DEBUG abort called

  After some troubleshooting I found that it was failing on calling 'snap debug connectivity'.
  Snap version I had was a bit old, which caused it to fail with panic on slice out of range.

  The issue is insufficient logging. Because of the actual error was not
  logged, It was impossible to find the issue without code debugging.

  It would be awesome if you can put more logs into
  _checkStoreConnectivity function and log stderr and stdout output from
  popen.communicate before calling self.controller.abort()

  Also it would be extremely useful to log traceback from abort. Can
  simplify the troubleshooting dramatically.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1810565/+subscriptions