should retry reading key from keyserver (in _recv_key)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-properties (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Some recent events have made keyservers less reliable than they were
previously:
https:/
https:/
We have seen a greatly increased failure rate of retreiving keys
from the key servers, both in cloud-init and with using apt-add-repository.
Here is an example failure:
https:/
The stdout/stderr that is a result of running:
$ add-apt-repository --yes ppa:cloud-
gpg: keyring `/tmp/tmp4s88x_
gpg: keyring `/tmp/tmp4s88x_
gpg: requesting key E4D304DF from hkp server keyserver.
gpgkeys: key 1FF0D8535EF7E71
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm
Failed to add key.
Retries on reading the key make sense here to be more resilient to
transient network or remote service resources. In apt-add-
case, the fingerprint is known to be good (as provided by launchpad)
so we know that it is not just a missing/incorrect key.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: software-
ProcVersionSign
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 28 22:28:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (1072 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Brian Murray: Needs Information
-
Diff: 171 lines (+92/-42)1 file modifiedsoftwareproperties/ppa.py (+92/-42)
- No reviews requested
tags: | added: rls-cc-incoming |
Status changed to 'Confirmed' because the bug affects multiple users.