Ah, thanks for that additional information! I was able to recreate this
issue by upgrading from bionic to focal and then running 'sudo ./focal
--frontend DistUpgradeViewText' in the folder in which the release
upgrader was extracted e.g. '/tmp/ubuntu-release-upgrader-nbgn2n5o'.
Perhaps the
Brian, answering comment#18, server upgraded has finished ~ 15h30`:
from logs: `=== Command detached from window (Tue Jul 21 15:23:36 2020) ===`
I just noticed it had bionic entries on sources.list when I was
installing bridge-utils:
```
Start-Date: 2020-07-21 16:28:23
Commandline: apt install
Ok. I see what I might have made wrong: trying to resurrect the session
(pressing 'r')
I was able to reproduce it just this way:
After it asks for upgrade:
```
If you select 'y' the system will be restarted.
Okay, I've one more idea. When the release upgrade process runs it
creates a backup of the sources.list file
(/etc/apt/sources.list.distUpgrade). Could you compare the "restored"
/etc/apt/sources.list file to the contents of
/etc/apt/sources.list.distUpgrade? I'd like to see a diff of the two
Thanks for the apt-clone file. I'm still not having any luck recreating
this issue though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with
Brian, sorry, I noticed that I've sent the wrong 'main.log' file
from `/var/log/dist-upgrade/20200721-1523/` instead of
`/var/log/dist-upgrade/`.
I'm attaching the correct one. Sorry!
** Attachment added: "/var/log/dist-upgrade/main.log"
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888916/+attachment/5399432/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The 20.04.1 point release is not out yet so I was running 'do-release-
upgrade -d'. I still don't see anything obvious in the log files the
directory '/var/log/dist-upgrade' should also contain a file name apt-
clone_system_state.tar.gz which is a snapshot of what the system looked
like before the
just wondering something, now we have the point release 20.04.1, when
I've upgraded the server it was not released yet, so I ran with `-d`:
`do-release-upgrade -d`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure. Comment #1 has screenlog.0. I'm adding the main.log:
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1888916/+attachment/5398909/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, I pressed 'x' to destroy the screen session. Could you provide
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/screenlog.0 so
I can try and sort out what's going on?
** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
How did you detach from the screen session?
I was able to reproduce the issue in a container pressing `x` on the screen
session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
I tried upgrading again with the /etc/molly-guard/rc changes on both an
Ubuntu 18.04 LTS desktop install (logged in via GUI) and a lxc container
(connected via ssh) and in neither case were the sources.list files set
back to bionic.
To finish the upgrade, a restart is required.
If you select 'y'
Brian, yes:
Configure to always ask for the hostname:
```
/etc/molly-guard/rc:
ALWAYS_QUERY_HOSTNAME=true
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to
** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with
I tried this both with an Ubuntu desktop install of 18.04 LTS and an lxc
cloud image of 18.04 LTS and during neither upgrade process did I
encounter the error described in this bug report. Here's some relevant
information from the lxc upgrade.
ubuntu@gorgeous-molly:~$ tail
Has some configuration of molly-guard been done that I also need to make
to recreate this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server
Ah my test in comment #4 was not via an ssh session, so that explains
why I didn't receive a message from molly-guard but it its not clear why
the system didn't reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried recreating this and while the system did not reboot sources.list
was not restored to bionic.
bdmurray@clean-bionic-amd64:~$ tail /var/log/dist-upgrade/screenlog.0
System upgrade is complete.
Restart required
To finish the upgrade, a restart is required.
If you select 'y' the system will
** Tags added: id-5f22e99071f5a889bf3c4734
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with molly-guard moves back
sources.list to bionic
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with molly-guard moves back
sources.list to bionic entries
To
Failure to call reboot, should not trigger rollback to previous suite.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with molly-guard moves back
** Also affects: ubuntu-release-upgrader (Ubuntu Groovy)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a
The release upgrader should be modified so that a failure to reboot is
not considered as a fail to upgrade and subsequently the sources.list
files should not be restored.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-release-upgrader
24 matches
Mail list logo
