do-release-upgrade does not work behind proxy

[Teemu Torma]

Binary package hint: update-manager-core

SourcePackage: update-manager
Package: update-manager-core 1:0.111.9
PackageArchitecture: amd64
ProblemType: Bug

When trying to do "do-release-upgrade -d" to upgrade Jaunty to Karmic beta, the process hangs. Even though the proxy setting is correct, it tries to connect directly to archive.ubuntu.com instead of using the proxy.

The reason is that Core.utils.url_downloadable does not appear to honor the proxy setting. Temporary hardwiring url_downloadable to always return True lets the process to go on and the upgrade succeeds.

[Mikael Davranche (plops2)]

I have exactly the same problem. Version 1:0.111.9 too.

[marcobra (Marco Braida) (marcobra)]

Same here... the "do-release-upgrade -d" hang without any informative message... :-(
trying to update Ubuntu 9.04 to Ubuntu 9.10 development post beta using a working proxy

Hope this helps

[DavidH (sajb)]

"Same here"..

After setting the http_proxy environment variable, I can use wget and similar and reach sites on the internet.. But running "do-release-upgrade -d" or running "update-manader -d" and clicking the "Upgrade" fails. The first only shows "Checking for a new ubuntu release" forever until I break (^C). The second needs to be killed.

Feels like https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/162996 never was fixed..

user@lab03:~$ export http_proxy="http://1.2.3.4:8080"
user@lab03:~$ sudo echo $http_proxy
http://1.2.3.4:8080
user@lab03:~$ sudo do-release-upgrade -d
Checking for a new ubuntu release
^CTraceback (most recent call last):
  File "/usr/bin/do-release-upgrade", line 61, in <module>
    fetcher.run()
  File "/usr/lib/python2.6/dist-packages/UpdateManager/Core/DistUpgradeFetcherCore.py", line 236, in run
    if not self.fetchDistUpgrader():
  File "/usr/lib/python2.6/dist-packages/UpdateManager/Core/DistUpgradeFetcherCore.py", line 203, in fetchDistUpgrader
    uri = self._expandUri(self.new_dist.upgradeToolSig)
  File "/usr/lib/python2.6/dist-packages/UpdateManager/Core/DistUpgradeFetcherCore.py", line 178, in _expandUri
    new_uri = self.mirror_from_sources_list(uri, self.DEFAULT_MIRROR)
  File "/usr/lib/python2.6/dist-packages/UpdateManager/Core/DistUpgradeFetcherCore.py", line 164, in mirror_from_sources_list
    if url_downloadable(mirror_uri, self._debug):
  File "/usr/lib/python2.6/dist-packages/UpdateManager/Core/utils.py", line 77, in url_downloadable
    c.request("HEAD", path)
  File "/usr/lib/python2.6/httplib.py", line 874, in request
    self._send_request(method, url, body, headers)
  File "/usr/lib/python2.6/httplib.py", line 911, in _send_request
    self.endheaders()
  File "/usr/lib/python2.6/httplib.py", line 868, in endheaders
    self._send_output()
  File "/usr/lib/python2.6/httplib.py", line 740, in _send_output
    self.send(msg)
  File "/usr/lib/python2.6/httplib.py", line 699, in send
    self.connect()
  File "/usr/lib/python2.6/httplib.py", line 683, in connect
    self.timeout)
  File "/usr/lib/python2.6/socket.py", line 505, in create_connection
    sock.connect(sa)
  File "<string>", line 1, in connect
KeyboardInterrupt

[marcobra (Marco Braida) (marcobra)]

As a workaround i have done...

After the first attempt of "sudo do-release-upgrade -d" restore the original /etc/apt/sources.list

sudo cp /etc/apt/sources.list.distUpgrade /etc/apt/sources.list

Then also check the result of "lsb_release -c", if you are upgrading from ubuntu 9.04 to Ubuntu 9.10, it must be:

lsb_release -c
Codename: jaunty

if it return:
Codename: karmic

You need to restore the old-release name in the /etc/lsb-release file

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"

Then export the http_proxy environment variable
export http_proxy=http://1.2.3.4:8080

and try again if the do-release-upgrade fails during the dl of packages simply redo the previuos step without clean the package cache. I do this 5 times and i get my system updated.

Hope this helps

[Launchpad Janitor (janitor)]

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