Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Unable to change ip_config after deployment #91

Open
justin-p opened this issue May 9, 2021 · 0 comments
Open

[BUG] Unable to change ip_config after deployment #91

justin-p opened this issue May 9, 2021 · 0 comments

Comments

@justin-p
Copy link

justin-p commented May 9, 2021

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.

  1. Nothing happens
  2. The cloud-init ip conifguration gets updated
  3. The user_account password is set to a unknown value
  4. 2 and 3 happen at the same time.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a VM
  2. Update the ip_config configuration
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant