Operational Defect Database
BugZero found this defect 1125 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4150
GPG error: The following signatures were invalid: KEYEXPIRED
Last update date:
10/31/2022
Affected products:
Veeam Backup for Nutanix AHV
Veeam Backup for AWS
Veeam Backup for Microsoft Azure
Affected releases:
1.0
Fixed releases:
No fixed releases provided.
Description:
Challenge
For the products of specific versions shown on this KB article when checking for updates or running 'apt-get update' from the terminal the task fails displaying the following error:
Cause
This occurs because the existing repository key for versions of products related to this article expired on April 16, 2021 (2021-04-16). Newer versions of the listed products are able to update the repository key automatically. For older versions, such as those listed on this article, users must manually remove the expired key and install the updated key.
Solution
Veeam Availability for Nutanix AHV 1.0 Veeam Backup for Nutanix AHV 2.0 Nutanix Mine 1.0 Nutanix Mine 2.0 Veeam Backup for AWS 1.0 Veeam Backup for AWS 2.0 Veeam Backup for Microsoft Azure 1.0
Veeam Backup for Nutanix AHV 1.0
SSH Disabled by Default SSH is disabled on Veeam Availability for Nutanix AHV by default, and as such access to the appliance must be performed via a Console as documented below. For more information about enabling SSH please see the Security Considerations section of the userguide.
Veeam Backup for Nutanix AHV 2.0
SSH Disabled by Default SSH is disabled on Veeam Availability for Nutanix AHV by default, and as such access to the appliance must be performed via a Console as documented below. For more information about enabling SSH please see the Enabling SSH section of the userguide.
Veeam Backup for AWS 1.0,2.0, Veeam Backup for Azure 1.0, Veeam PN
Log in to the shell of the appliance machine. Run the following commands to remove the expired repository key and add a new one
More Information
If after updating the repository key the 'apt-get update' command still displays errors, please open a support case.
