Open sorinpad opened 8 months ago
This issue is stale because it has been open for 30 days with no activity and it has not the 'status: confirmed' label or it is not in a milestone. Remove the 'status: stale' label or comment, or this will be closed in 5 days.
Sorry for the late reply, it seems it was a small error in the code, feel free to test the fix in the PR I just created
Description
Creation of a VM group is successful, subsequent runs do not try to modify the resource.
In practice, Terraform tries to update VM group with all but the first host in the
host_anti_affined
attribute.Terraform and Provider version
Terraform: 1.3.9, 1.4.6, 1.5.7 Provider: 1.2.2, 1.3.1
Affected resources and data sources
opennebula_virtual_machine_group
Terraform configuration
Expected behavior
The VM group gets created with a role called
random
which lists the 11 hosts in the anti_affined list.Actual behavior
The VM Group gets created with a role called
random
which lists the 11 hosts in the anti_affined list, however, on subsequent runs, Terraform tries to add all but the last host to the anti_affined list.Steps to Reproduce
Create a VM group:
Run the plan again; Terraform wants to add all but the first host in the list:
Trying to apply the change fails (but that's on Nebula's API side), stating the group has some VMs attached:
We can see Nebula itself already has the hosts in the VM group:
Debug output
No response
Panic output
No response
Important factoids
No response
References
No response