| 2018-04-10 15:52:57 |
Graham Leggett |
bug |
|
|
added bug |
| 2018-04-10 15:53:28 |
Graham Leggett |
summary |
apt-get update hangs when apt-transport-https is no installed |
apt-get update hangs when apt-transport-https is not installed |
|
| 2018-04-10 16:36:26 |
Julian Andres Klode |
apt (Ubuntu): status |
New |
Fix Released |
|
| 2018-04-10 16:56:24 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-04-10 16:56:24 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Xenial) |
|
| 2018-04-10 16:56:31 |
Julian Andres Klode |
apt (Ubuntu Xenial): status |
New |
Triaged |
|
| 2018-04-10 16:57:07 |
Julian Andres Klode |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870675 |
|
| 2018-04-10 16:57:07 |
Julian Andres Klode |
bug task added |
|
apt (Debian) |
|
| 2018-04-10 22:03:37 |
Bug Watch Updater |
apt (Debian): status |
Unknown |
Fix Released |
|
| 2018-04-11 10:36:41 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Trusty |
|
| 2018-04-11 10:36:41 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Trusty) |
|
| 2018-04-11 10:36:48 |
Julian Andres Klode |
apt (Ubuntu Trusty): status |
New |
Triaged |
|
| 2018-06-26 11:08:38 |
Julian Andres Klode |
apt (Ubuntu Trusty): status |
Triaged |
In Progress |
|
| 2018-06-26 11:08:44 |
Julian Andres Klode |
apt (Ubuntu Trusty): status |
In Progress |
Confirmed |
|
| 2018-06-26 11:08:46 |
Julian Andres Klode |
apt (Ubuntu Trusty): status |
Confirmed |
Triaged |
|
| 2018-06-26 11:08:47 |
Julian Andres Klode |
apt (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2018-06-27 15:38:40 |
Chris J Arges |
apt (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2018-06-27 15:38:41 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-06-27 15:38:44 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2018-06-27 15:38:47 |
Chris J Arges |
tags |
|
verification-needed verification-needed-xenial |
|
| 2018-06-28 09:45:10 |
Julian Andres Klode |
description |
When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs.
The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally.
The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed.
Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns.
Key notes:
- The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not.
- The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears.
- We encountered this on a host that didn't support cut and paste, sorry :( |
[Impact]
Two or more sources with an unknown protocol cause apt update to hang
[Test case]
Add two or more sources with an unknown protocol and run update
[Regression potential]
This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods.
[Original bug report]
When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs.
The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally.
The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed.
Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns.
Key notes:
- The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not.
- The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears.
- We encountered this on a host that didn't support cut and paste, sorry :( |
|
| 2018-06-28 09:45:44 |
Julian Andres Klode |
description |
[Impact]
Two or more sources with an unknown protocol cause apt update to hang
[Test case]
Add two or more sources with an unknown protocol and run update
[Regression potential]
This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods.
[Original bug report]
When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs.
The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally.
The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed.
Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns.
Key notes:
- The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not.
- The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears.
- We encountered this on a host that didn't support cut and paste, sorry :( |
[Impact]
Two or more sources with an unknown protocol cause apt update to hang. For example, when using the https method on a system without integrated https support and without apt-transport-https installed.
[Test case]
Add two or more sources with an unknown protocol and run update
[Regression potential]
This changes the code to only register a method that actually exists. I don't see any potential for a regression here, but of course, if there were any, it would be related to not finding other methods.
[Original bug report]
When "apt-get update" is run on a docker container running Ubuntu v16.04 and containing an additional apt source repository hosted on an https webserver, the "apt-get update" command hangs.
The hang happens after connections to http ubuntu hosts are complete, and apt-get remains stuck on "Working" at 0%. Removing the sources file for the https repo causes apt-get to complete normally.
The source file contains 4 separate entries to 4 different repos on the same https server. When the source file is modified so that just *one* entry exists to one repo on the https server, we suddenly get a sensible error message that tells us that apt-transport-https needs to be installed.
Installing apt-transport-https into the docker container before adding the sources list to the https servers works around the problem and sanity returns.
Key notes:
- The use of docker isn't related to the bug, except that the docker image doesn't contain the apt-transport-https package whereas our cloud images do contain this package by default. This can give the impression that this is a docker bug when it's not.
- The hang in "apt-get update" seems to occur when the sources file contains more than one entry in the file. When just one entry exists in the file (and all other entries are commented out) a sensible error messages appears.
- We encountered this on a host that didn't support cut and paste, sorry :( |
|
| 2018-06-28 14:19:35 |
Julian Andres Klode |
tags |
verification-needed verification-needed-xenial |
verification-done verification-done-xenial |
|
| 2018-07-05 07:55:15 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-07-05 07:55:22 |
Launchpad Janitor |
apt (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
