-
Notifications
You must be signed in to change notification settings - Fork 510
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
[gpu] apt-get update Init script seeing broken repositories #1129
Comments
Thank you! I'll get a PR opened shortly. |
Please use the latest 2.0 image if you are using an older version of 2.0 image in your dataproc cluster creation script. There was a change in public key of mysql repo in Dec'2023 because of which you might be facing the issue. With a recent image I am able to see it working fine
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a new Dataproc cluster using the install_gpu_driver.sh init script results in the following two issues:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.mysql.com/apt/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7B3B788A8D3785C
=> Current workaround is to remove the MySQL repository from being updated via:
mv /etc/apt/sources.list.d/mysql.list /tmp/mysql.list
E: Repository 'https://packages.cloud.google.com/apt google-cloud-monitoring-buster-all InRelease' changed its 'Origin' value from 'google-cloud-monitoring-buster' to 'namespaces/cloud-ops-agents-artifacts/repositories/google-cloud-monitoring-buster-all' E: Repository 'https://packages.cloud.google.com/apt google-cloud-monitoring-buster-all InRelease' changed its 'Label' value from 'google-cloud-monitoring-buster' to 'namespaces/cloud-ops-agents-artifacts/repositories/google-cloud-monitoring-buster-all'
=> Workaround is to allow for the repository change:
apt-get --allow-releaseinfo-change update
Full log:
The text was updated successfully, but these errors were encountered: