Veeam repo GPG expired?

[G_Mellor]

Hi,
I'm trying to install Veeam Backup for Salesforce for the first time, but I'm coming across the following issue:

Code: Select all

Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature

If I download the GPGkey repomd.xml.key file (https://repository.veeam.com/yum/el/8/x ... md.xml.key) and try and check it manually:

Code: Select all

$ curl -s https://repository.veeam.com/yum/el/8/x86_64/repodata/repomd.xml.key | gpg2
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2018-04-27 [SC] [expired: 2024-03-24]
      1DD6EAD9AF6E8F34465D790CEA4FC237EFDCEA77
uid           Veeam Software RPM Repository <support@veeam.com>
sub   rsa4096 2018-04-27 [E] [expired: 2024-03-24]

I'm in Australia, so it's already mid afternoon on the 25th March here - should this GPG signature have been renewed before now?

Although it's Veeam Backup for Salesforce that I'm trying to install, this appeared to be a wider issue hence posting here rather than under VBFS.

Cheers,
Gary

[Andrew Razumovskiy]

Should be fixed now

[G_Mellor]

Hi Andrew,

It appears the CDN fronting the repository is taking a while to refresh down here in Australia - it's still showing as "Bad GPG signature" for me.

If I look via my web browser at https://repository.veeam.com/yum/el/8/x86_64/repodata/, the directory listing there shows the repomd.xml dated from 28th November last year. However if I use a VPN to Europe or America then the files show as updated on 25th March - so your CDN node nearest me in Australia is either slow to refresh or isn't picking up updates.

I'll check again later to see if the CDN's caught up.

Cheers for sorting the root cause,
Gary.

[Andrew Razumovskiy]

Fixed, please try now

[ChristianS]

Andrew,

I'm just trying to run a

Code: Select all

sudo yum update

on my server and get the same error message. I'm on Oracle Linux Server release 8.9
Looks like the issue is persisting.

Thanks,
Chris

[Andrew Razumovskiy]

try run

Code: Select all

yum clean all

and then again

Code: Select all

yum update

Also, we've refreshed cache for repository once again (just in case)

[ChristianS]

Thank you, Andrew. This fix worked