Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Has GPG key of apt repo expired? #2860

Closed
MatthewFagan opened this issue Jan 16, 2023 · 14 comments
Closed

Has GPG key of apt repo expired? #2860

MatthewFagan opened this issue Jan 16, 2023 · 14 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@MatthewFagan
Copy link

apt-get update returns the following error:
Err:4 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05

This occurred previously in #1982. Is there a problem with new key distribution? Is this a known issue and expected to get fixed soon?
@MatthewFagan MatthewFagan added area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Jan 16, 2023
@dims
Copy link
Member

dims commented Jan 17, 2023

xref : #2862

@dims dims mentioned this issue Jan 17, 2023
Closed
@lukeweller
Copy link

I'm seeing the same issue on my Ubuntu 20.04.5 machine:

$ sudo apt update             
...
Err:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
W: Failed to fetch https://apt.kubernetes.io/dists/kubernetes-xenial/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
W: Some index files failed to download. They have been ignored, or old ones used instead.

@delta1
Copy link

delta1 commented Jan 19, 2023

This fixed it for me

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add -

@bueti
Copy link

bueti commented Jan 23, 2023

it seems like the new key isn't deployed everywhere because even when adding the new key manually I get intermittent errors

@afolarin
Copy link

it seems like the new key isn't deployed everywhere because even when adding the new key manually I get intermittent errors

Yes, same here.

@elitistphoenix
Copy link

elitistphoenix commented Jan 30, 2023 •
edited
Loading

Ditto as per @afolarin
Hopefully nothing dodgy going on.
Since you're in the UK and I'm in Aus

@sftim
Copy link
Contributor

sftim commented Feb 4, 2023

kubernetes/enhancements#1731 is tracking work to address this

@bryfry bryfry mentioned this issue Feb 12, 2023
Closed
@raykrueger raykrueger mentioned this issue Feb 26, 2023
Closed
@raykrueger
Copy link

raykrueger commented Feb 26, 2023 •
edited
Loading

The apt-key-gpg url seems to be giving 500 errors from random places in the world. I setup a health check with AWS Route 53 and see the following results. The dns and https GETs will happen from each of the regions below. Hopefully this is useful data.

Health checker region Health checker IP Last checked Status  
Asia Pacific (Tokyo) 15.177.42.9 Feb 26, 2023 7:32:49 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.199.110  
Asia Pacific (Tokyo) 15.177.46.9 Feb 26, 2023 7:32:18 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.207.46  
Asia Pacific (Singapore) 15.177.54.9 Feb 26, 2023 7:33:18 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.4.138  
Asia Pacific (Singapore) 15.177.50.11 Feb 26, 2023 7:33:19 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 172.217.194.102  
Asia Pacific (Sydney) 15.177.58.9 Feb 26, 2023 7:33:21 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.204.14  
Asia Pacific (Sydney) 15.177.62.9 Feb 26, 2023 7:33:21 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.66.206  
EU (Ireland) 15.177.34.9 Feb 26, 2023 7:33:18 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 74.125.193.101  
EU (Ireland) 15.177.38.9 Feb 26, 2023 7:33:18 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 172.253.116.113  
South America (São Paulo) 15.177.26.9 Feb 26, 2023 7:33:19 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.218.174  
South America (São Paulo) 15.177.30.9 Feb 26, 2023 7:33:19 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.79.206  
US East (N. Virginia) 15.177.6.9 Feb 26, 2023 7:33:16 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 172.253.122.102  
US East (N. Virginia) 15.177.2.11 Feb 26, 2023 7:33:16 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.251.16.102  
US West (N. California) 15.177.10.9 Feb 26, 2023 7:33:18 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.46.238  
US West (N. California) 15.177.14.9 Feb 26, 2023 7:33:17 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.214.142  
US West (Oregon) 15.177.22.9 Feb 26, 2023 7:33:17 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.69.206  
US West (Oregon) 15.177.18.9 Feb 26, 2023 7:33:17 PM UTC Failure: HTTP Status Code 500, Internal Server Error. Resolved IP: 142.250.217.110

@jaydesl jaydesl mentioned this issue Feb 26, 2023
Merged
4 tasks
@bueti
Copy link

bueti commented Feb 27, 2023

once again, google rotates keys w/o updating all locations 🤦

@bueti
Copy link

bueti commented Feb 27, 2023

workaround suggested by google support: GoogleCloudPlatform/gcsfuse#961 (comment)

@dims dims mentioned this issue Feb 27, 2023
Merged
@dims
Copy link
Member

dims commented Feb 27, 2023

See work around with new URL here: kubernetes/k8s.io#4837 (comment)

@cpanato
Copy link
Member

cpanato commented Feb 27, 2023

key are back https://packages.cloud.google.com/apt/doc/apt-key.gpg

/close

@k8s-ci-robot
Copy link
Contributor

@cpanato: Closing this issue.

In response to this:

key are back https://packages.cloud.google.com/apt/doc/apt-key.gpg

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@raykrueger
Copy link

Confirmed that the gpg health checks are all passing now.

Health checker region Health checker IP Last checked Status  
Asia Pacific (Tokyo) 15.177.42.9 Feb 27, 2023 7:38:31 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.199.110  
Asia Pacific (Tokyo) 15.177.46.9 Feb 27, 2023 7:38:49 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.42.174  
Asia Pacific (Singapore) 15.177.54.9 Feb 27, 2023 7:38:44 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.4.139  
Asia Pacific (Singapore) 15.177.50.11 Feb 27, 2023 7:38:54 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 172.253.118.102  
Asia Pacific (Sydney) 15.177.58.9 Feb 27, 2023 7:38:46 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.204.14  
Asia Pacific (Sydney) 15.177.62.9 Feb 27, 2023 7:38:44 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.66.206  
EU (Ireland) 15.177.34.9 Feb 27, 2023 7:38:28 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 74.125.193.113  
EU (Ireland) 15.177.38.9 Feb 27, 2023 7:38:50 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 74.125.193.100  
South America (São Paulo) 15.177.26.9 Feb 27, 2023 7:38:40 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.132.238  
South America (São Paulo) 15.177.30.9 Feb 27, 2023 7:38:34 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.129.174  
US East (N. Virginia) 15.177.6.9 Feb 27, 2023 7:38:55 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 172.253.122.101  
US East (N. Virginia) 15.177.2.11 Feb 27, 2023 7:38:45 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.16.138  
US West (N. California) 15.177.10.9 Feb 27, 2023 7:38:41 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.250.189.174  
US West (N. California) 15.177.14.9 Feb 27, 2023 7:38:34 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.46.238  
US West (Oregon) 15.177.22.9 Feb 27, 2023 7:38:39 PM UTC Success: HTTP Status Code 200, OK. Resolved IP: 142.251.33.78

@raykrueger raykrueger mentioned this issue Feb 27, 2023
Closed
@a-hilaly a-hilaly mentioned this issue Sep 5, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/bug Categorizes issue or PR as related to a bug. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests