Open bjvrielink opened 3 years ago
@bjvrielink Did you ever find a workaround for this?
I worked around this by changing how the domain connects to the network. What I had was:
resource "libvirt_domain" "this" {
network_interface {
network_id = var.network_id
}
}
I refactored my code into:
resource "libvirt_domain" "this" {
network_interface {
bridge = var.network
}
}
System Information
Linux distribution
Alpine Linux v3.13
Terraform version
Provider and libvirt versions
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?
[X] 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
Each and every time I run terraform plan or apply, terraform-provider-libvirt wants to change the network interfaces of the VM's.
Setup
Steps to Reproduce Issue
When terraform plan runs, it wants to change the network interface:
This change does not impact the running VM. The risk is that when you have a changed resource each and every time you run terraform plan, there will be a day that you overlook another change (on the same resource) that has impact.
Additional information:
I run terraform as a docker container (hashicorp/terraform:latest) as part of a Gitlab CI pipeline. The docker host has SELinux, but not in a way that should affect this issue.