You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I’m encountering an issue with Terraform’s libvirt provider when using a TLS-enabled URI (e.g., qemu+tls://node.example.com/system). Terraform hangs indefinitely when running apply or plan. In contrast, the SSH URI works without any problems.
Setup
Terraform is executed from macbook (certs located in ~/.pki/libvirt).
Set up CA certificates on the host running libvirt. Since my host is an IPA client, I added a service, generated certificates, and placed them in the expected libvirt paths.
Store client certs on macbook in ~/.pki/libvirt
Verify access to libvirt node:
virsh -c qemu+tls://node.example.com/system list
If successful, you should something like this (my host has no domains):
Id Name State
--------------------
Create aforementioned main.tf then run:
terraform init
TF_LOG=TRACE terraform plan
Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration? Have you tried to reproduce the issue without them enabled?
Firewall and SELinux were disabled in the process of debugging
RHEL 9+ now uses modular libvirt daemons instead of the monolithic libvirt daemon by default. Not sure if that's related.
The text was updated successfully, but these errors were encountered:
System Information
Linux distribution
RHEL 9.5
Terraform version
Provider and libvirt versions
terraform-provider-libvirt -
0.8.1
libvirt -
10.5.0
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?
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
I’m encountering an issue with Terraform’s libvirt provider when using a TLS-enabled URI (e.g., qemu+tls://node.example.com/system). Terraform hangs indefinitely when running apply or plan. In contrast, the SSH URI works without any problems.
Setup
Terraform is executed from macbook (certs located in
~/.pki/libvirt
).main.tf
Steps to Reproduce Issue
Set up CA certificates on the host running libvirt. Since my host is an IPA client, I added a service, generated certificates, and placed them in the expected libvirt paths.
Store client certs on macbook in
~/.pki/libvirt
Verify access to libvirt node:
If successful, you should something like this (my host has no domains):
Create aforementioned
main.tf
then run:Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration? Have you tried to reproduce the issue without them enabled?
The text was updated successfully, but these errors were encountered: