Instances with custom image family are planned to be recreated

[matdtr]

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 me too comments, 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.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

v0.15.5
v1.0.6
google v4.1.0

Affected Resource(s)

• google_compute_instance

Terraform Configuration Files

resource "google_compute_instance" "test" {
  project = "XXXXX"
  name         = "test"
  zone         = "europe-west3-a"
  machine_type = "n1-standard-1"
  boot_disk {
    initialize_params {
      image = "projects/YYYYYYY/global/images/family/ZZZZZZ" 
      size = 50
    }
  }
  shielded_instance_config {
    enable_secure_boot = false
    enable_vtpm = true
    enable_integrity_monitoring = true
  }
  lifecycle {
    ignore_changes = [attached_disk]
  }
}

Expected Behavior

No changes. Infrastructure is up-to-date.

Actual Behavior

The VM is recreated everytime Terraform is run since it thinks the image changed.

Steps to Reproduce

1. terraform plan
2. terraform apply

[matdtr]

Any update ?

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.