All logs from there:
2019-01-03 21:02:19,137 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2019-01-03 21:02:19,137 INFO uname information: 'Linux skashaba-laptop
4.4.0-83-gene
ric #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64'
2019-01-03 21:02:19,410 INFO apt version: '1.2.20'
2019-01-03 21:02:19,137 INFO uname information: 'Linux skashaba-laptop
4.4.0-83-gene
ric #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64'
2019-01-03 21:02:19,410 INFO apt version: '1.2.20'
2019-01-03 21:02:19,411 INFO python version: '3.5.2 (default, Nov 17 2016,
17:05:23)
[GCC 5.4.0
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
FRom: 16.04 LTS
To: 18.04 LTS
Snippet of the function that maid the troubleshooting process painful:
https://pastebin.com/pFdSRP0e
I don't have all the details, since that upgrader was downloaded to /tmp
folder that gone away after reboot.
--
You received this bug notification because you are
** Description changed:
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
Public bug reported:
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
