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
Describe the bug
Once the VM has been deployed by Terraform the module is unable to update the cloud-init ip configuration. After applying the updated Terraform code the module trows the following error.
proxmox_virtual_environment_vm.ubuntu_vm: Modifying... [id=4321]
╷
│ Error: Received an HTTP 500 response - Reason: lvcreate 'pve/vm-4321-cloudinit' error: Logical Volume "vm-4321-cloudinit" already exists in volume group "pve"
│
│ with proxmox_virtual_environment_vm.ubuntu_vm,
│ on main.tf line 34, in resource "proxmox_virtual_environment_vm" "ubuntu_vm":
│ 34: resource "proxmox_virtual_environment_vm" "ubuntu_vm" {
│
╵
On the proxmox side either one of these 4 things could happen.
Nothing happens
The cloud-init ip conifguration gets updated
The user_account password is set to a unknown value
2 and 3 happen at the same time.
To Reproduce
Steps to reproduce the behavior:
Deploy a VM
Update the ip_config configuration
Terraform apply
Expected behavior
Updating the ip_config in Terraform sets the new IP in the cloud-init user-data. No changes to the user_account should be applied.
The text was updated successfully, but these errors were encountered:
Describe the bug
Once the VM has been deployed by Terraform the module is unable to update the cloud-init ip configuration. After applying the updated Terraform code the module trows the following error.
On the proxmox side either one of these 4 things could happen.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Updating the ip_config in Terraform sets the new IP in the cloud-init user-data. No changes to the user_account should be applied.
The text was updated successfully, but these errors were encountered: