terraform-provider-libvirt: Signing key expired?
System Information
Linux distribution
Ubuntu 23.04
Terraform version
> terraform -v
Terraform v1.6.0
on linux_amd64
Checklist
-
Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?
- Make sure you explain why this option is important to you, why it should be important to everyone. Describe your use-case with detail and provide examples where possible.
- If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
- Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation
-
Is it a bug or something that does not work as expected? Please make sure you fill the version information below:
Description of Issue/Question
The provider cannot be installed, as the key used to sign it seems to have expired.
Setup
main.tf
terraform {
required_providers {
libvirt = {
source = "dmacvicar/libvirt"
version = "0.7.1"
}
}
}
Steps to Reproduce Issue
Just trying to initialize a new main.tf with the provider should be enough.
> terraform init
Initializing the backend...
Initializing provider plugins...
- Finding dmacvicar/libvirt versions matching "0.7.1"...
- Installing dmacvicar/libvirt v0.7.1...
╷
│ Error: Failed to install provider
│
│ Error while installing dmacvicar/libvirt v0.7.1: error checking signature: openpgp: key expired
╵
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 5
- Comments: 18 (6 by maintainers)
For now, if you roll back to 1.5.7 you should be good. Worked for me.
Yeah, same issue here. Looks like PGP keys are expired/revoked.
Ubuntu 22.04, Terraform:
Ok pals, v0.7.4 should be working. Reopen if having problems.
El mismo error hoy 10-Oct-2023: │ Error: Failed to install provider │ │ Error while installing dmacvicar/libvirt v0.7.2: checksum list has unexpected SHA-256 hash │ 7d634ac045a8593bdac82e3ae40589d81900262373caafbfa28c4d7c54bf91cb (expected │ 6a2ee6c7b448462d81d4aa4b2d2bf0b25b1c1f3438c646e7e601f6e583bdfb18)
I’m experiencing the same issue just now:
I have rebuild again. Now the registry complains about the hash. It seems the registry is caching the old build 😦
I am looking into it, and publish a new release.
Just FYI this is caused by what seems to be an unintentional breaking change in
v1.6.0