vmware / terraform-provider-vra

Terraform Provider for VMware Aria Automation
https://registry.terraform.io/providers/vmware/vra/
Mozilla Public License 2.0
101 stars 89 forks source link

Adding a vra_network that a vra_machine is connected to does not make the physical change #525

Closed PaulAngus closed 2 months ago

PaulAngus commented 2 months ago

Code of Conduct

This project has a Code of Conduct that all participants are expected to understand and follow:

vRA Version

8.16.1

Terraform Version

1.7.0

vRA Terraform Provider Version

0.9.0

Affected Resource(s)

vra_machine

Terraform Configuration Files

Initial configuration

data "vra_network" "network" {
  name = var.vmnetworkname
}

resource "vra_machine" "vm" {
  name          = var.vmname
  flavor        = var.vmflavorname
  image         = var.vmimagename
  project_id    = data.vra_project.project.id

  nics {
    network_id = data.vra_network.network.id
}

Updated configuration:

data "vra_network" "net1" {
  name = var.vm1networkname
}

data "vra_network" "net2" {
  name = var.vm1network2name
}

resource "vra_machine" "vm1" {
  name        = var.vm1name
  description = var.vm1description
  project_id  = data.vra_project.project1.id
  image       = var.vm1imagename
  flavor      = var.vm1flavorname

  nics {
    network_id = data.vra_network.net1.id
  }

  nics {
    network_id = data.vra_network.net2.id
  }
}

Expected Behavior

Adding a vra_network to an existing vra_machine and re-running terraform apply should add the additional network to the machine.

Actual Behavior

Terraform immediately returns that the modifications are complete. However, no changes have been made. It does not appear that any attempt is made to make this change.

Steps to Reproduce

Create a deployment with the a vra_machine connected to a network, add an additional network to the vra_machine and re-run terraform apply.

Screenshots

Debug Output

Panic Output

Important Factoids

References

Community Note

frodenas commented 2 months ago

@Thanks for reporting the issue @PaulAngus. I'm going to close this issue and consolidate the nic update issue it at #524.