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

[Steve Dodd]

This hit me trying to run a container upgrade in an environment where
snapd wasn't running. Not a supported situation I'm sure but the extra
logging would be good - just capturing the "snap debug connectivity"
output and dumping to log would be fine..

-- 
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:
  Confirmed

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