[Bug 2002945] Re: dist-upgrade failed in many unpredictabl ways

[Nick Rosbrook]

The reason this is "invalid" for ubuntu-release-upgrader is that there
does not appear to be any actionable information here that is specific
to ubuntu-release-upgrader. It would be more effective if you opened a
bug report against the appropriate package for each of the issues you
experienced. I will try to provide a bit more direction to help you
create bug reports that can potentially be investigated further.

> - I have launched the upgrade from command line apt dist-upgrade as
the GUI tool was not doing nothing, not event reporting a message. There
was a packet holding back, I have uninstalled it with synaptic and then
apt dist-upgrade started

Which package was causing this problem? What do you mean by "holding
back"? If you believe $PACKAGE was causing update-manager to fail,
please open a bug report against $PACKAGE describing the issue.

- Still the boot did not start. I was thinking that maybe some package
is misconfigured, I have run apt update but there was no internet
connection, and ifconfig was telling me that net-tools were not
installed. I have entered rescue mode, I have re-anabled the networking,
then check the dependency, and then the boot started.

I'm not sure there are enough details for me to point you in the right
direction here. But if you can figure out what package was causing the
problem, you can open a bug report against that package.

> - The boot failed. I have looked in the log and an apparmor profile
was blocking the boot, because one file could not be parsed. The error
was in the mysql file that can not be parsed. I have moved this in
another folder and this error message was gone.

Was the file /etc/apparmor.d/abstractions/mysql? What was the error? If
you can provides those details, you should open a bug against the
apparmor package.

> - But still, the computer was booting just in rescue mode. I have
looked into the logs (because the journalctl command was not reporting
any failure) and I have seen that a partition could not be found. It was
an nfts partition that I have created to share data between ubuntu and
windows (I have a dual boot installation). I have commented out that
line in /etc/fstab and it worked. But stil I did not understand why it
can not be read anymore. ntfs-3g and fuse are installed, it should work
as before.

Without logs, it is hard to immediately tell which package to blame for
this. A good start would be to open a bug against systemd (because it
parses /etc/fstab to generate mount units), and describe your partition
scheme, and what entry from /etc/fstab had to be removed to fix the
system.

Hopefully this helps.

-- 
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/2002945

Title:
  dist-upgrade failed in many unpredictabl ways

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

Bug description:
  I haven't find a better place to report my experience, without any doubts the worst dist-upgrade since 8 years. I have finally fixed everything but it was a real pain. I will describe here what went wrong, in the hope that the next dist-upgrade will be better.
  - I have launched the upgrade from command line apt dist-upgrade as the GUI tool was not doing nothing, not event reporting a message. There was a packet holding back, I have uninstalled it with synaptic and then apt dist-upgrade started

  - The boot failed. I have looked in the log and an apparmor profile was blocking the boot, because one file could not be parsed. The error was in the mysql file that can not be parsed. I have moved this in another folder and this error message was gone.
  - Still the boot did not start. I was thinking that maybe some package is misconfigured, I have run apt update but there was no internet connection, and ifconfig was telling me that net-tools were not installed. I have entered rescue mode, I have re-anabled the networking, then check the dependency, and then the boot started.
  - But still, the computer was booting just in rescue mode. I have looked into the logs (because the journalctl command was not reporting any failure) and I have seen that a partition could not be found. It was an nfts partition that I have created to share data between ubuntu and windows (I have a dual boot installation). I have commented out that line in /etc/fstab and it worked. But stil I did not understand why it can not be read anymore. ntfs-3g and fuse are installed, it should work as before.

  Anyway, to recap:
  1) graphical upgrade tool was not able to report which package was holding back the upgrade process
  2)the mysql file in snap can not be parsed and that blocked the boot, measure a bit too excessive IMHO
  3)network was unreacheable because some basic programs were uninstalled
  4)NFTS partition was unreadable and the journalctl command, was not reporting the name of the failed partition

  Now everything works again and looks good, except the nfts partition.
  I do not think this is the right place were to report my upgrade
  experience, but I think it might be helpful to improve our beloved
  Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.15
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 16 09:52:14 2023
  InstallationDate: Installed on 2017-12-02 (1870 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2023-01-13  17:04:34
   Install: libgc1:amd64 (1:8.0.6-1.1build1, automatic)
   Upgrade: guile-2.2-libs:amd64 (2.2.7+1-4, 2.2.7+1-6build2)
   Remove: libgc1c2:amd64 (1:7.6.4-0.4ubuntu1)
   End-Date: 2023-01-13  17:04:36

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