Loading...
Loading...
In Veeam Backup for Salesforce v1, the Updater displays no updates available despite the fact that newer versions are available.
The updater fails to identify new updates as being available because of an expired or incorrect GPG key used to verify package integrity. Without the proper GPG key, the package manager cannot authenticate or apply updates correctly, resulting in errors during update attempts. When this occurs, the Veeam-updater.log will contain the following error: Service.CheckUpdates: Cannot find any updates for VBSF repository (<guid>): packageManagerErrorFailedGetList veeam-repo exit code: 1, timeout exceeded: false, output: , errors: Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature
Use the following scripts to switch to the correct GPG key:
Newer versions of Veeam Backup for Salesforce handle updating the repo GPG keys more effectively, which is why this issue eclusively affects Veeam Backup for Salesforce version 1.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.