Update' action is not supported after importing a deployment

mf-sky commented 1 year ago

Code of Conduct

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

[X] I have read and agree to the project's Code of Conduct

vRA Version

Version 8.11.1.29538 (21309636)

Terraform Version

Terraform v1.5.4 on darwin_arm64

vRA Terraform Provider Version

provider registry.terraform.io/vmware/vra v0.7.3

Affected Resource(s)

vra_deployment

Terraform Configuration Files

resource "vra_deployment" "vdc-slave-vm32" {
  name                 = "vdc-slave-vm32"
  description          = ""
  catalog_item_id      = data.vra_catalog_item.ubuntu.id
  catalog_item_version = var.catalog_item_version
  project_id           = data.vra_project.project.id

}

Expected Behavior

State updated according to terraform file

Actual Behavior

Plan reports changes. When applying those changes (with the imported values), fails with: Error: noticed changes to inputs, but 'Update' action is not supported based on the current state of the deployment vdc-slave-vm32

Steps to Reproduce

Create deployment via UI
Import resource to terraform
Retrofit terraform file so that it has the inputs declared. This gives visibility on resources when changing terraform and enables me to resize accordingly

Screenshots

N/A

Debug Output

Panic Output

N/A

Important Factoids

N/A

References

Ill reference https://github.com/vmware/terraform-provider-vra/issues/170. Not sure if its the same issue

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

mf-sky commented 1 year ago

As a test, i deleted the original deployment. Started from scratch using terraform

resource "vra_deployment" "vdc-slave-vm32" {
  name                 = "vdc-slave-vm32"
  description          = ""
  catalog_item_id      = data.vra_catalog_item.ubuntu.id
  catalog_item_version = var.catalog_item_version
  project_id           = data.vra_project.project.id

  inputs = {
    "cpus"                  = "2"
    "memory"                = "2048"
  }

  timeouts {
    create = "30m"
    delete = "30m"
    update = "30m"
  }
}

After this creation i changed the memory value, did a terraform apply expecting to get a resize and got Error: noticed changes to inputs, but 'Update' action is not supported based on the current state of the deployment vdc-slave-vm32

gthieleb commented 11 months ago

I have the same issue when the deployment was deleted outside of terraform.

module.simple_vm.vra_deployment.this: Modifying... [id=62ffde89-3224-4d0f-b109-f9c8d2256da4]
╷
│ Error: noticed changes to inputs, but 'Update' action is not supported based on the current state of the deployment
│
│   with module.simple_vm.vra_deployment.this,
│   on .terraform/modules/simple_vm/main.tf line 49, in resource "vra_deployment" "this":
│   49: resource "vra_deployment" "this" {

mmn01-sky commented 10 months ago

Having the same issue. I can't seem to increase cpu or memory on any of my deployments.

Error:

vra_deployment.jumphost[0]: Modifying... [id=ad943186-8025-4e3d-8dc5-c4f35381a7d4]
╷
│ Error: noticed changes to inputs, but 'Update' action is not supported based on the current state of the deployment POC Cluster HHE - Jumphost
│ 
│   with vra_deployment.jumphost[0],
│   on machine-jumphost.tf line 28, in resource "vra_deployment" "jumphost":
│   28: resource "vra_deployment" "jumphost" {
│ 
╵

an2ane commented 10 months ago

Does your deployment have the Update action available in vRA? Looks like it is not.

The error message is coming from the resource_deployment.go file, and it is trying to fetch the day-2 action from deployment.

mmn01-sky commented 10 months ago

@an2ane we've raised this to our engineering team who look after the vRA platform. They will review and report back to us with any updates.

mf-sky commented 10 months ago

Works! Update action is available. Thanks @an2ane for the insight and @mmn01-sky for testing. Closing the issue.

vmware / terraform-provider-vra