[Bug 822910] Re: 6.06 upgrade fails due to bad repo?

[Robb Breckenridge]

Hi Per,

I think we are experiencing different issues.

Here's my output of "do-release-upgrade"..
http://pastebin.com/6zQHQNyn


R

----- Original Message -----
From: "Per Cederqvist" <822910 at bugs.launchpad.net>
To: "not robb" <not.robb at gmail.com>
Sent: Tuesday, August 9, 2011 12:57:22 PM
Subject: [Bug 822910] Re: 6.06 upgrade fails due to bad repo?

Robb, you did not describe exactly what happened when you attempted to
upgrade.  I'm having trouble upgrading a 8.10 server, and the root cause
of both our problems may be that the UpgradeTool of
http://changelogs.ubuntu.com/meta-release points to non-existing URLs
for both 8.10 and 6.06.

When I run "sudo do-release-upgrade" I get the following output:

  Checking for a new ubuntu release
  Failed Upgrade tool signature
  Failed Upgrade tool
  Done downloading            
  extracting 'jaunty.tar.gz'
  Failed to extract
  Extracting the upgrade failed. There may be a problem with the network or with the server. 

Not very helpful.  Using strace I'm able to retrive the real error
messages:

  sudo strace -f -s 70000 -o /tmp/release.strace  do-release-upgrade

Afterwards, in the /tmp/release.strace file I can see that it fetches the meta-release file
and stores it in /var/lib/update-manager/meta-release.  It seems to try to use the 
UpgradeTool URL from that file to retrieve jaunty.tar.gz.  I see this error message:

  28281 <... read resumed> "400 URI Failure\nURI:
http://archive.ubuntu.com/ubuntu/dists/jaunty-proposed/main/dist-
upgrader-all/0.111.8/jaunty.tar.gz\nMessage: 404 Not Found [IP:
91.189.88.45 80]\nFailReason: HttpError404\n\n", 64000) = 192

If I change the URI of /etc/update-manager/meta-release from 
http://changelogs.ubuntu.com/meta-release to http://www.lysator.liu.se/~ceder/tmp/meta-old
(where I have blindly replaced all "archive" with "old-releases") things work slightly better.
The jaunty.tar.gz file is accepted.  But after a while I get these messages:

  Hit http://old-releases.ubuntu.com intrepid-security/universe Packages
  Hit http://old-releases.ubuntu.com intrepid-security/multiverse Packages
  Done downloading            
  Reading package lists: Done
  Reading state information: Done
  Reading state information: Done
  Reading state information: Done
  
  Updating repository information
  
  No valid mirror found 
  
  While scanning your repository information no mirror entry for the 
  upgrade was found.This can happen if you run a internal mirror or if 
  the mirror information is out of date. 
  
  Do you want to rewrite your 'sources.list' file anyway? If you choose 
  'Yes' here it will update all 'intrepid' to 'jaunty' entries. 
  If you select 'no' the update will cancel. 
  
  Continue [yN] 

If I restore the /etc/update-manager/meta-release file and run this

  echo  91.189.88.140 archive.ubuntu.com | sudo tee -a /etc/hosts

things work even better.  The IP address actually belongs to old-releases.ubuntu.com.
Now I get all the way to

  Do you want to start the upgrade?


  1 package is going to be removed. 57 new packages are going to be 
  installed. 828 packages are going to be upgraded. 

  You have to download a total of 430M. This download will take about 7 
  minutes with your connection. 

  Fetching and installing the upgrade can take several hours. Once the 
  download has finished, the process cannot be cancelled. 

   Continue [yN]  Details [d]

...and here I bail out because I cannot actually update the server until 
the service window on 2011-08-15.

Sorry to spam if this was totally irrelevant to the original problem.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/822910

Title:
  6.06 upgrade fails due to bad repo?

Status in “update-manager” package in Ubuntu:
  Incomplete

Bug description:
  Trying to upgrade a server from 6.06 to 8.04.
  I think it's failing because it can't find http://archive.ubuntu.com/ubuntu dapper-backports main/debian-installer

  That missing repo seems to automatically get added to
  /etc/apt/sources.list.d/prerequists-sources.dapper.list

  I have do not have any backports enabled in /etc/apt/sources.list.
  I've tried commenting out the line in prerequists-sources.dapper.list
  and making the file read-only, but it still gets added when I try to
  upgrade.

  Is this something you're able to update on the copy of prerequists-
  sources.dapper.list that gets pushed out?

  Here is a copy of /etc/apt/sources.list and /etc/apt/sources.list.d/prerequists-sources.dapper.list   -- Happy to provide more info if it's useful.......
  http://pastebin.com/vnsfvvdq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/822910/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/822910

Title:
  6.06 upgrade fails due to bad repo?

Status in “update-manager” package in Ubuntu:
  Incomplete

Bug description:
  Trying to upgrade a server from 6.06 to 8.04.
  I think it's failing because it can't find http://archive.ubuntu.com/ubuntu dapper-backports main/debian-installer

  That missing repo seems to automatically get added to
  /etc/apt/sources.list.d/prerequists-sources.dapper.list

  I have do not have any backports enabled in /etc/apt/sources.list.
  I've tried commenting out the line in prerequists-sources.dapper.list
  and making the file read-only, but it still gets added when I try to
  upgrade.

  Is this something you're able to update on the copy of prerequists-
  sources.dapper.list that gets pushed out?

  Here is a copy of /etc/apt/sources.list and /etc/apt/sources.list.d/prerequists-sources.dapper.list   -- Happy to provide more info if it's useful.......
  http://pastebin.com/vnsfvvdq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/822910/+subscriptions