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?
No
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.
My assumption is that if others were using an SSH connection and ran into this issue, they would want to know the default/expected behaviours.
If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
I feel like this warrants an issue, as to be it is not a special case.
Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation
docs detailing supported extra parameters on the URI for libvirt.
Is it a bug or something that does not work as expected? Please make sure you fill in the version information below:
Plan: 1 to add, 0 to change, 0 to destroy.
╷
│ Error: failed to connect: failed to read ssh known hosts: open ~/.ssh/known_hosts: no such file or directory
│
│ with provider["registry.terraform.io/dmacvicar/libvirt"],
│ on providers.tf line 2, in provider "libvirt":
│ 2: provider "libvirt" {
If I then change my connection string to uri = "qemu+ssh://[email protected]/system?knownhosts=/home/dustin/.ssh/known_hosts" it will work. I also tested with uri = "qemu+ssh://[email protected]/system?knownhosts=~/.ssh/known_hosts" which also failed. It seems like it no longer understands ~.
Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
No
Have you tried to reproduce the issue without them enabled?
No (NA)
I noted that the SSH Config stuff was reworked for 0.8.0. Is this behaviour intended?
Thank you in advance.
The text was updated successfully, but these errors were encountered:
System Information
Linux distribution
Terraform version
Provider and libvirt versions
Checklist
No
My assumption is that if others were using an SSH connection and ran into this issue, they would want to know the default/expected behaviours.
I feel like this warrants an issue, as to be it is not a special case.
docs detailing supported extra parameters on the URI for libvirt.
Description of Issue/Question
Setup
variables.tf
provider.tf
extensions.tf
main.tf
network.tf
volumes.tf
controlplane.tf
worker.tf
Steps to Reproduce Issue
terraform init
terraform plan
Error
If I then change my connection string to
uri = "qemu+ssh://[email protected]/system?knownhosts=/home/dustin/.ssh/known_hosts"
it will work. I also tested withuri = "qemu+ssh://[email protected]/system?knownhosts=~/.ssh/known_hosts"
which also failed. It seems like it no longer understands~
.Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration?
Have you tried to reproduce the issue without them enabled?
I noted that the SSH Config stuff was reworked for
0.8.0
. Is this behaviour intended?Thank you in advance.
The text was updated successfully, but these errors were encountered: