do-release-upgrade could notify when release is expected

Bug #1605474 reported by Bharath on 2016-07-22
304
This bug affects 58 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
High
Unassigned

Bug Description

So, today is July 21st and this page (http://www.ubuntu.com/download/server). gives me an option to download 16.04.1 LTS. However, attempting to upgrade gets me this message -

$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found

I asked this question here - http://askubuntu.com/questions/801488/how-do-i-upgrade-from-14-04-lts-server-to-16-04-1

The best answer I got is that the update log is not updated - http://changelogs.ubuntu.com/meta-release-lts

The last entry here is -

```
Dist: trusty
Name: Trusty Tahr
Version: 14.04.4 LTS
Date: Thu, 17 Apr 2014 14:04:00 UTC
Supported: 1
Description: This is the 14.04.4 LTS release
Release-File: http://archive.ubuntu.com/ubuntu/dists/trusty/Release
ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/ReleaseAnnouncement
ReleaseNotesHtml: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html
UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/trusty.tar.gz
UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/trusty.tar.gz.gpg
```

Bharath (lord-loh) on 2016-07-22
description: updated
description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
summary: - Problems upgrading from 14.04LTS to 16.04.1
+ "No new release found" upgrading from 14.04LTS to 16.04.1

I used the following workaround which appears to work fine and gives me 16.04.1 LTS (upgrading from 14.04.4 LTS):

    do-release-upgrade -d

Bharath (lord-loh) wrote :
andrew (andrew-david-strong) wrote :

I can confirm this bug on my Trusty system...

MikeR (mike-rechtman) wrote :

+1

If this is a feature and not a bug then
a) a more detailed explanation would be nice
b) when may we expect the update-manager to behave as expected.

Bharath (lord-loh) wrote :

@mike-rechtman: How does this look like a feature request?

Any way the ASK ubuntu answer has a comment from Thomas Ward that he heard from the release team that release upgrades would be open after a week.

description: updated
Pirx Danford (pirxdanford) wrote :

Cheers, so I was going by https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule and its really difficult to find information about why LTS server systems won't upgrade.

There are a lot of people suggestiong to use the -d flag, but quite frankly I don't feel like taking that risk. So I hope the documentation about the waiting time and its reasons will improve.

The way I understand it now if @Bharath is correct with availability after a week we could expect do-dist-upgrade to offer the update on July the 28th?
It would be very cool if this very important step in the upgrade process would be reflected in the schedule, after all its about upgrading LTS servers, which are normally pretty vital infrastructure wise.

"After a week" is in the comment to the answer on Ask Ununtu. A moderator
got this info from IRC. And there is nothing to stop them from making it a
fortnight.

On Jul 25, 2016 2:50 AM, "Pirx Danford" <email address hidden> wrote:

> Cheers, so I was going by
> https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule and its really
> difficult to find information about why LTS server systems won't
> upgrade.
>
> There are a lot of people suggestiong to use the -d flag, but quite
> frankly I don't feel like taking that risk. So I hope the documentation
> about the waiting time and its reasons will improve.
>
> The way I understand it now if @Bharath is correct with availability after
> a week we could expect do-dist-upgrade to offer the update on July the 28th?
> It would be very cool if this very important step in the upgrade process
> would be reflected in the schedule, after all its about upgrading LTS
> servers, which are normally pretty vital infrastructure wise.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1605474
>
> Title:
> "No new release found" upgrading from 14.04LTS to 16.04.1
>
> Status in ubuntu-release-upgrader package in Ubuntu:
> Confirmed
>
> Bug description:
> So, today is July 21st and this page
> (http://www.ubuntu.com/download/server). gives me an option to
> download 16.04.1 LTS. However, attempting to upgrade gets me this
> message -
>
> $ sudo do-release-upgrade
> Checking for a new Ubuntu release
> No new release found
>
> I asked this question here - http://askubuntu.com/questions/801488
> /how-do-i-upgrade-from-14-04-lts-server-to-16-04-1
>
> The best answer I got is that the update log is not updated -
> http://changelogs.ubuntu.com/meta-release-lts
>
> The last entry here is -
>
> ```
> Dist: trusty
> Name: Trusty Tahr
> Version: 14.04.4 LTS
> Date: Thu, 17 Apr 2014 14:04:00 UTC
> Supported: 1
> Description: This is the 14.04.4 LTS release
> Release-File: http://archive.ubuntu.com/ubuntu/dists/trusty/Release
> ReleaseNotes:
> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/ReleaseAnnouncement
> ReleaseNotesHtml:
> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html
> UpgradeTool:
> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/trusty.tar.gz
> UpgradeToolSignature:
> http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/dist-upgrader-all/current/trusty.tar.gz.gpg
> ```
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1605474/+subscriptions
>

Yes, using do-release-upgrade -d does read the meta-release file at http://changelogs.ubuntu.com/meta-release-lts-development. The relevant part of that file is UpgradeTool and that line will be the same when we add 16.04 to meta-release-lts. The Ubuntu release team is still keeping an eye for bugs regarding the upgrade process and will update the meta-release-lts file shortly.

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
Bharath (lord-loh) wrote :

@brian-murray: Knowing this is reassuring. I'll consider trying the `-d` option :-)

Bharath (lord-loh) wrote :

It might be helpful if the error message said -

$ sudo do-release-upgrade
Checking for a new Ubuntu release
No new release found - Next release expected to be available on 2016-06-28.

The meta file cold have an entry for the next release in the schedule. This would save a lot of people a lot of time and trouble. I think I shall post this as a separate feature request.

Added: https://answers.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+question/303763

Bharath (lord-loh) on 2016-07-26
summary: - "No new release found" upgrading from 14.04LTS to 16.04.1
+ "No new release found" upgrading from 14.04LTS to 16.04.1 [Bug + Feature
+ Request]

The meta-release-lts file has been updated now.

http://changelogs.ubuntu.com/meta-release-lts

summary: - "No new release found" upgrading from 14.04LTS to 16.04.1 [Bug + Feature
- Request]
+ do-release-upgrade could notify when release is expected
Bharath (lord-loh) wrote :

Thank you. If the developers do indeed decide to implement such a feature, it would be good if some custom message could be shown. Something like - "We are waiting to squash all the bugs." So if the expected date passes by and no one has updated the revised ETA date, people have reassurance that there is a reason this is happening and not a flaw / bug.

Achim Behrens (k1l) wrote :

As already said in https://bugs.launchpad.net/ubuntu/+bug/1606850 :

i really suggest the release-team chases the bugs before the .1 release and opens the LTS upgrade on the .1 release.

As you can see here on comment #2 people want to upgrade and the internet is full of the wrong advice to use the -d, --devel-release setting.

I dont see a technical reason to delay the LTS upgrade.
So i hope on the next LTS release cycle the schedule will make sure the bugtesting is done before the .1 release. The supporter teams will give thanks for that.

Jared Feng (indeed) wrote :

I see meta-release-lts is now up-to-date with 16.04.1 There is no trouble updating now.

Joan (aseques) wrote :

Just in case anyone needs it, the downloaded file is cached at /var/lib/update-manager/meta-release-lts, I had and issue that my firewall blocked the site and the error page was stored here.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions