[Bug 1766542] Re: Installation blocks when the machine is behind a proxy server

[Brian Murray]

I don't believe that any special fix is need for ubiquity given that the
bug and fix were in apt, so I'm setting this task to Invalid.

** Changed in: ubiquity (Ubuntu Bionic)
       Status: New => Invalid

** Tags removed: rls-bb-incoming

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Invalid

Bug description:
  [Impact]
  APT takes a long time to notice when certain connections time out

  [Test case]
  * Change the default route to not route stuff successfully (wrong gateway,
    for example)
  * Make your sources.list look like this:

  deb http://archive.ubuntu.com/ubuntu bionic main restricted
  deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted

  * Run apt update

  You should see that it fails with a long verbose error message for the
  first entry, with all possible IP addresses listed in it; while for
  the second one it fails with just "Unable to connect to
  archive.ubuntu.com:http:" as it recognizes it has been blacklisted.

  [Regression potential]
  APT will not attempt to retry the host given that it could not connect to it for previous entries. If your network recovered in the meantime, it might update less than previously.

  [Original bug report]
  When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions