Should I be offered the option to upgrade to 18.04.1?

Question

I understand that the first point release of Ubuntu 18.04, namely 18.04.1 is now available and that my system should now offer it as an update.

My current OS version is 16.04.5 LTS. In System Settings/Software and Updates I have set 'Notify me of a new Ubuntu version' to 'For long term support versions'. I have tried both the main server and the server for United Kingdom, neither offers an update when Software Updater is clicked or via the Ubuntu Software icon.

Can anyone please tell me why I don't get the option of updating to 18.04?

Edit:

I don't remember the details exactly, but I think that my last LTS point release update was offered automatically a lot sooner after the published release date than where we are now with 18.04.1.

Edit 10th August

It appears that there has been some problem with the update process and that it should be fixed next week, see:

Ubuntu change log

Edit 14th August 18.04.1 LTS now available from UK server,

Answer 1

The upgrade from 16.04 LTS to 18.04 LTS does not occur until the .1 release has been out. The usual procedure is the 'taps' are turned on a few days after the .1 release. Currently we're only hours after the release, not 'days', so the update will not be offered quite yet.

It's mentioned in the release notes:

"Users of Ubuntu 16.04 will soon be offered an automatic upgrade to 18.04.1 via Update Manager."

-- update 2018-08-08 ~04:30 UST/UTC

It may soon be available; if this is the 'critical' bug holding up release (https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890) - it only impacts 16.04 LTS -> 18.04 LTS upgrades. 18.04.1 is stable; it's the upgrade-path that is turned-off..

-- update 2018-08-10 ~10:10 UST/UTC

https://lists.ubuntu.com/archives/ubuntu-release/2018-August/004556.html

"We are working on resolving bug http://launchpad.net/bugs/1766890 which results in a bad upgrade experience when people upgrade to Ubuntu 18.04. There is a new version of the dist-upgrader in -proposed and we will be testing it the next couple of days and plan on updating meta-release-lts at the beginning of next week."

Answer 2

For anyone still receiving the "No release found" error several days after 18.04.1, this process worked for me to upgrade from 16.04.5 to 18.04.1:

Software & Updates > Updates > Notify me of a new Ubuntu Version > Select "For Any New Version" > Open Software Updater

For some reason, "For long-term support versions" was not notifying me about 18.04.1 LTS.

Once I changed it to "For any new version" I was immediately prompted to upgrade to 18.04.1. The upgrade has run without issue.

Mahalo to deadflowr for originally suggesting this fix here: https://ubuntuforums.org/showthread.php?t=2397703

Answer 3

Guiverc, you seem to have the best fix on this. You indicated that forcing the upgrade (-d) worked well for you. Does this still work unattended, or will a relative newbie like me get into difficulties? Is the "official" release likely to be within an additional day or two so that we should be patient? Do you have any sense what kinds of problems are holding up the official release?

Addendum: I run Ubuntu from a VBox virtual machine. So I cloned my 16.04 version and ran sudo do-release-upgrade -d.

• a) The update worked and completed without hitch and without any need for user intervention. All of my most important apps seem to work fine.
• b) There were a number of warnings about configuration files that were missing or directories that couldn't be deleted, but these issues seem to have been dealt with later in the update.
• c) One issue should be noted. The update program warned me that the xenial R source entry in my /etc/apt/sources file had been commented out, but noted that I could reactivate it after completing the update. Unfortunately there doesn't seem yet to be a Ubuntu R bionic repository. Fortunately both R and RStudio appear to be updated correctly within the apps, but I suspect that I won't be told of updates of R by the Ubuntu Update app. In sum, it seems that using the -d option for the Ubuntu update from 16.04 to 18.04 works well. But NO GUARANTEES. Larry Hunsicker

Answer 4

The do-release-upgrade command is a Python script. After some digging I discovered that it respects presence of 'DEBUG_UPDATE_MANAGER' in environment.

Typing:

$ export DEBUG_UPDATE_MANAGER=1
$ do-release-upgrade

results in:

[... some lines skipped ...]
metarelease-uri: https://changelogs.ubuntu.com/meta-release-lts
MetaRelease.download()
result of meta-release download: **'<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:645)>'**
NO self.metarelease_information
No new release found.

So the core reason seems to be the inability to verify the SSL certificate presented by changelogs.ubuntu.com