-
Notifications
You must be signed in to change notification settings - Fork 439
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.
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
Issue at https://packages.cloud.google.com/apt/doc/apt-key.gpg - Non Resolving URL #961
Comments
We created a workaround to this we thought we'd share. Based on taking the latest version release one can simply forego the Google recommended installation using the gpg key and simply install the release as debian package. Since our requirement was for a docker image, our RUN command appears as follows...
This correctly installed what we needed without dealing with the dependency on the down URL. If anyone believes removing the dependency on the gpg and recommended reference to the down URL will have any negative affects now or down the road please share. |
Hii @christian-screen, Thanks for reaching out to us. That was standard procedure to install gcsfuse via an apt-key update, but you can install it with this procedure, also. There will be no negative effects on that. |
Workaround:
and similar commands can be replaced with
as verified by a cached wayback machine page from 5 days ago. |
Thank you @tennysontbardwell! I verified that the provided base64 matched the the way back machines files as well. Here is my result of making use of the cached GPG key workaround in a github actions workflow file. jobs:
test-gke-plugin-setup:
runs-on: ubuntu-22.04
steps:
- run: |
REPO_URL="https://packages.cloud.google.com/apt"
echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] $REPO_URL cloud-sdk main" | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list >/dev/null
# FIXME: A cached version of a gpg key is used from the way back
# machine, dated 2023-02-23.
#
# https://web.archive.org/web/20230223152417/https://packages.cloud.google.com/apt/doc/apt-key.gpg
#
# The live gpg key at https://packages.cloud.google.com/apt/doc/apt-key.gpg
# is inaccessible with a HTTP 500 response.
#
# When the live gpg key is available agian, we can revert to doing this:
#
# sudo wget -q https://packages.cloud.google.com/apt/doc/apt-key.gpg -O /usr/share/keyrings/cloud.google.gpg
#
echo "xsBNBGKItdQBCADWmKTNZEYWgXy73FvKFY5fRro4tGNa4Be4TZW3wZpct9Cj8EjykU7S9EPoJ3EdKpxFltHRu7QbDi6LWSNA4XxwnudQrYGxnxx6Ru1KBHFxHhLfWsvFcGMwit/znpxtIt9UzqCm2YTEW5NUnzQ4rXYqVQK2FLG4weYJ5bKwkY+ZsnRJpzxdHGJ0pBiqwkMT8bfQdJymUBown+SeuQ2HEqfjVMsIRe0dweD2PHWeWo9fTXsz1Q5abiGckyOVyoN9//DgSvLUocUcZsrWvYPaN+o8lXTO3GYFGNVsx069rxarkeCjOpiQOWrQmywXISQudcusSgmmgfsRZYW7FDBy5MQrABEBAAHNUVJhcHR1cmUgQXV0b21hdGljIFNpZ25pbmcgS2V5IChjbG91ZC1yYXB0dXJlLXNpZ25pbmcta2V5LTIwMjItMDMtMDctMDhfMDFfMDEucHViKcLAYgQTAQgAFgUCYoi11AkQtT3IDRPt7wUCGwMCGQEAAMGoCAB8QBNIIN3Q2D3aahrfkb6axd55zOwR0tnriuJRoPHoNuorOpCv9aWMMvQACNWkxsvJxEF8OUbzhSYjAR534RDigjTetjK2i2wKLz/kJjZbuF4ZXMynCm40eVm1XZqU63U9XR2RxmXppyNpMqQO9LrzGEnNJuh23icaZY6no12axymxcle/+SCmda8oDAfa0iyA2iyg/eU05buZv54MC6RB13QtS+8vOrKDGr7RYp/VYvQzYWm+ck6DvlaVX6VB51BkLl23SQknyZIJBVPm8ttU65EyrrgG1jLLHFXDUqJ/RpNKq+PCzWiyt4uy3AfXK89RczLu3uxiD0CQI0T31u/IzsBNBGKItdQBCADIMMJdRcg0Phv7+CrZz3xRE8Fbz8AN+YCLigQeH0B9lijxkjAFr+thB0IrOu7ruwNY+mvdP6dAewUur+pJaIjEe+4s8JBEFb4BxJfBBPuEbGSxbi4OPEJuwT53TMJMEs7+gIxCCmwioTggTBp6JzDsT/cdBeyWCusCQwDWpqoYCoUWJLrUQ6dOlI7s6p+iIUNIamtyBCwb4izs27HdEpX8gvO9rEdtcb7399HyO3oD4gHgcuFiuZTpvWHdn9WYwPGM6npJNG7crtLnctTR0cP9KutSPNzpySeAniHx8L9ebdD9tNPCWC+OtOcGRrcBeEznkYh1C4kzdP1ORm5upnknABEBAAHCwF8EGAEIABMFAmKItdQJELU9yA0T7e8FAhsMAABJmAgAhRPk/dFj71bU/UTXrkEkZZzE9JzUgan/ttyRrV6QbFZABByf4pYjBj+yLKw3280//JWurKox2uzEq1hdXPedRHICRuh1Fjd00otaQ+wGF3kY74zlWivB6Wp6tnL9STQ1oVYBUv7HhSHoJ5shELyedxxHxurUgFAD+pbFXIiK8cnAHfXTJMcrmPpC+YWEC/DeqIyEcNPkzRhtRSuERXcq1n+KJvMUAKMD/tezwvujzBaaSWapmdnGmtRjjL7IxUeGamVWOwLQbUr+34MwzdeJdcL8fav5LA8Uk0ulyeXdwiAK8FKQsixI+xZvz7HUs8ln4pZwGw/TpvO9cMkHogtgzQ==" | base64 -d | sudo tee -a /usr/share/keyrings/cloud.google.gpg
sudo apt-get update -y
sudo apt-get install -y google-cloud-sdk-gke-gcloud-auth-plugin |
Can someone share ansible workaround also? My current ansible task is below:
Also, Is it a temp issue or |
For ansible, I made it work like:
Save this apt-key.gpg on your package repository and use that package repostory url for your task. |
It is an ongoing bug regarding the apt-get key, not the gcsfuse bug. We will update this thread once it gets fixed. |
still facing this issue |
Anyone facing the same issue with chef packages used for Jenkins? Any workaround available as we are seeing Production impact due to this issue. Update:- Performed a workaround to copy cached GPG key to local artifactory repo inorder to unblock Jenkins pipeline |
Facing the same issue when installing gcloud cli |
Using the workaround mentioned in GoogleCloudPlatform/gcsfuse#961 (comment) to unblock the e2e tests. Signed-off-by: Sascha Grunert <[email protected]>
Hi, this fails for me with anisble returning the following error: Unable to extract key from 'inline data'", "stderr": "gpg: WARNING: no command supplied |
Using the workaround mentioned in GoogleCloudPlatform/gcsfuse#961 (comment) to unblock the e2e tests. Signed-off-by: Sascha Grunert <[email protected]>
Using the workaround mentioned in GoogleCloudPlatform/gcsfuse#961 (comment) to unblock the e2e tests. Signed-off-by: Sascha Grunert <[email protected]>
For Ansible try this:
|
You can try:
|
Using the workaround mentioned in GoogleCloudPlatform/gcsfuse#961 (comment) to unblock the e2e tests. Signed-off-by: Sascha Grunert <[email protected]>
In Ubuntu I fixed it by using the following command to get the key from a trusted mirror: I have tried other suggestions without any luck. |
Have the same problem |
FYI the Kubernetes project is rehosting the key at https://dl.k8s.io/apt/doc/apt-key.gpg, see kubernetes/k8s.io#4837 |
I'm able to build Docker images again while using the WaybackMachine URI, will probably just stick with the Kube one though. Here's the RUN command I used in my Dockerfile for anyones ref..
|
@sig-flores It's not really future-proof, I would not stick with it tbh |
is there an estimate on when this will be fixed? would rather not have to impliment these work arounds |
working here now
|
yup working for me too now |
Using the workaround mentioned in GoogleCloudPlatform/gcsfuse#961 (comment) to unblock the e2e tests. Signed-off-by: Sascha Grunert <[email protected]>
Any plans to publish the postmortem? |
Same here. |
Issue is resolved:
|
I am going through the same problem with this installation step of Kubectl on my CI/CD. It seems that curl is outdated. I temporarily resolved it by just ignoring this step because my runner already has Kubectl installed and there's no risk of losing this installation since the container won't be restarted. If you need to, configure it if you're using your own runner. .I hope it's helpful |
As per https://issuetracker.google.com/issues/270841451#comment3 the HTTP/500 response when retrieving this specific URL / GPG key on Google Cloud under some condition should be resolved. |
Yes, It is working. apt-key is available now. |
If you are using a notebook in colab this is my work around. The issue was fixed and is not occurring again. %%shell curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - |
It looks issue has been resolved, but feel free to open it again if anything comes up. |
Heyo it's not working for me today but it's working with https://dl.k8s.io/apt/doc/apt-key.gpg |
Its working now. Can you check again. |
I have the same issue today and using the key suggested by @mar-pan fixed it for me. |
Worked like a charm. Thank you! |
Describe the bug
Attempting the Standard debian/ubuntu gpg reference per installation documentation, the URI is not available (is there an alternative URL or a mirror), https://packages.cloud.google.com/apt/doc/apt-key.gpg, the page and CuRl attempt provides the following:
`
<title>Error 500 (Internal Server Error)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/logos/errorpage/error_logo-150x54-2x.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style>500. That’s an error.
That’s all we know.`
To Collect more Debug logs
Steps to reproduce the behavior:
System (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: