1

I just upgraded a 14.04 server to 16.04 using the standard do-release-upgrade process. Now I'm getting "No new release found" when trying to run it again to get to 18.04.

Things tried:

  • sudo apt update
  • sudo apt upgrade
  • sudo apt dist-upgrade
  • sudo apt full-upgrade
  • sudo do-release-upgrade ("No new release found.")
  • sudo do-release-upgrade -d ("Upgrades to the development release are only available from the latest supported release.")
  • sudo do-release-upgrade -p ("No new release found.")
  • wget http://changelogs.ubuntu.com/meta-release (successfully gets the file, it shows the correct data including the 18.04 info)
  • sudo apt install update-manager-core ("update-manager-core is already the newest version (1:16.04.17).")
  • vim /etc/update-manager/release-upgrades (prompt is set to "lts" as expected)

Questions:

  • Why isn't 18.04 being found and offered to upgrade? I don't understand how do-release-upgrade works under the hood and why it'd throw "no new release found" when it is successfully accessing the meta-release file, the file has the correct data and there is a newer LTS release with a point version out.
  • How do I upgrade this machine? What is the best and safest workaround?
2
  • Which "development release" appears on do-release-upgrade -d? Probably updates are disabled in Software & Updates. – Pilot6 May 6 '20 at 15:19
  • It doesn't show any release. Just says that error. Are you talking about the GUI Software & Updates? This machine doesn't have a GUI installed. – thunderblaster May 6 '20 at 15:20
0

Please try installing the ca-certificates package and then running 'do-release-upgrade'. The fix for this issue is in progress you can follow it via https://launchpad.net/bugs/1796940.

4
  • ca-certificates is already installed and up-to-date. Looks like the usual indicator of that issue is Failed to connect to https://changelogs.ubuntu.com/meta-release-development. Check your Internet connection or proxy settings, which is not the result I'm experiencing. – thunderblaster May 8 '20 at 13:04
  • 1
    Could you paste the output of "DEBUG_UPDATE_MANAGER=1 do-release-upgrade"? – Brian Murray May 8 '20 at 17:18
  • You're a hero. It's a cert error and it's because of the corporate content filtering. – thunderblaster May 8 '20 at 17:51
  • If you wanted to post an answer explaining the use of DEBUG_UPDATE_MANAGER, I'd gladly accept it. I googled around and didn't come across that, and it's exactly the sort of additional info I was looking for to debug that extremely opaque error. – thunderblaster May 8 '20 at 17:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.