Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.grid.uchicago.edu
* epel: mirror.steadfastnet.com
* extras: mirror.den01.meanservers.net
* updates: mirror.compevo.com
google-cloud-logging/x86_64/signature | 844 B 00:00:00
Retrieving key from https://packages.cloud.google.com/yum/doc/yum-key.gpg
Importing GPG key 0xA7317B0F:
Userid : "Google Cloud Packages Automatic Signing Key <gc-...@google.com>"
Fingerprint: d0bc 747f d8ca f711 7500 d6fa 3746 c208 a731 7b0f
From : https://packages.cloud.google.com/yum/doc/yum-key.gpg
Is this ok [y/N]: y
Retrieving key from https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
google-cloud-logging/x86_64/signature | 1.4 kB 00:00:13 !!!
https://packages.cloud.google.com/yum/repos/google-cloud-logging-el7-x86_64/repodata/repomd.xml: [Errno -1] repomd.
xml signature could not be verified for google-cloud-logging
Trying other mirror.
This turns out to be a known issue for which we have a workaround.
What you need to do to get this working is to disable repository GPG key checking in the yum repo configuration by setting repo_gpgcheck=0. This is likely set in /etc/yum.repos.d/google-cloud.repo however it may be possible you have this set in other repository configuration files or automation tools.
Yum repositories don’t usually use GPG keys for their repository validation. Instead, the HTTPS endpoint is trusted. CentOS doesn’t use GPG key checks for their repositories.
So, change all lines that repo_gpgcheck=1 to repo_gpgcheck=0.
The team is working on changing this by default, but we’re not able to alter existing environments.