GPG key issues causing package update failures
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nginx, python
- Domain
- devops, infrastructure
Research direction
Start with the failed package update output for planet.nyc1.psf.io and review the referenced Python issue #568 for the Ubuntu 18.04 and Python 2 constraints. Trace where the datadog, nginx, and Salt repository keys are configured; done means package updates no longer fail signature verification without breaking the host's supported setup.
Written by the indexing model from the issue text.
Description
May be able to fix by updating to new keys (datadog, nginx, salt) but also this host is far out of support range (18.04) but is stuck due to python2 (See: https://github.com/python/planet/issues/568#issue-2417204196)
Summary for planet.nyc1.psf.io
--------------
Succeeded: 161 (changed=3)
Failed: 3
...
----------
ID: python-requests
Function: pkg.latest
Result: False
Comment: An error was encountered while checking the newest available version of package(s): W: GPG error: http://nginx.org/packages/mainline/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62
E: The repository 'http://nginx.org/packages/mainline/ubuntu bionic InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.datadoghq.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E6266D4AC0962C7D
W: GPG error: https://packages.broadcom.com/artifactory/saltproject-deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 64CBBC8173D76B3F
E: The repository 'https://packages.broadcom.com/artifactory/saltproject-deb stable InRelease' is not signed.
Started: 18:17:06.302980
Duration: 6061.297 ms
Changes:
...
----------
ID: consul-external-console
Function: consul.external_service
Name: console
Result: False
Comment: One or more requisite failed: base.salt.python-requests
Started: 18:17:13.456682
Duration: 0.012 ms
Changes:
----------
ID: consul-external-jobs
Function: consul.external_service
Name: jobs
Result: False
Comment: One or more requisite failed: base.salt.python-requests
Started: 18:17:13.457442
Duration: 0.005 ms
Changes:
----------
...
- Dominant language
- Hurl
- Stars
- 124
- Forks
- 67
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/psf-salt
-
codespeed
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
infra mail
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
python/psf-salt#618 · 12 comments · 1 reaction · 1 assignee ·
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Azure/azure-functions-docker#1257 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
conda-forge/vowpalwabbit-feedstock#104 · 1 comment · 1 reaction ·
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
deploy.sh hardcodes --dest while components.conf advertises WITH_PROXY_CA_BUNDLE as env-overridable Openarea:proxy bug security severity:low track:open-source
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
components-web-app/docs#73 ·