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

google_container_engine_versions or google_compute_network does not plan [3.40.0 β†’ 3.41.0] #7379

Closed
miseyu opened this issue Sep 29, 2020 · 10 comments

Comments

@miseyu
Copy link

miseyu commented Sep 29, 2020

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

  • Terraform v0.13.0
  • provider.google v3.41.0

Affected Resource(s)

  • google_container_engine_versions
  • google_compute_network

Terraform Configuration Files

data "google_container_engine_versions" "version" {
  location       = local.zones.tokyo-a
  project        = var.pjname
  version_prefix = "1.16."
}

resource "google_compute_network" "network" {
  name    = "${var.pjname}-network"
  project = var.pjname

  auto_create_subnetworks = "false"

  routing_mode = "REGIONAL"
}

Debug Output

Error: Invalid resource instance data in state

  on cluster.tf line 1:
   1: data "google_container_engine_versions" "version" ***

Instance data.google_container_engine_versions.version data could not be
decoded from the state: unsupported attribute "region".


Error: Invalid resource instance data in state

  on cluster.tf line 1:
   1: data "google_container_engine_versions" "version" ***

Instance data.google_container_engine_versions.version data could not be
decoded from the state: unsupported attribute "region".


Error: Invalid resource instance data in state

  on network.tf line 1:
   1: resource "google_compute_network" "network" ***

Instance google_compute_network.network data could not be decoded from the
state: unsupported attribute "ipv4_range".


Error: Invalid resource instance data in state

  on network.tf line 1:
   1: resource "google_compute_network" "network" ***

Instance google_compute_network.network data could not be decoded from the
state: unsupported attribute "ipv4_range".
@essjayhch
Copy link

For clarity, this effects v0.12 as well as 0.13, but that is probably self-evident as it will have been a change in the provider configuration

@Jean-Mercier
Copy link

same root cause than issue
#7381

@slevenick
Copy link
Collaborator

Hey @miseyu I believe this is an issue with Terraform core, and I believe it was fixed in version 0.13.1 by this PR: hashicorp/terraform#25779

Can you (or anyone else seeing this bug) try upgrading your version of Terraform to see if it works for you?

I can reproduce by using 0.13.0 but not 0.13.3.

@slevenick
Copy link
Collaborator

Closing as I believe this is not a provider bug. Please reopen this if upgrading Terraform to 0.13.1+ does not fix the issue for you

@jamesyale
Copy link

Closing as I believe this is not a provider bug. Please reopen this if upgrading Terraform to 0.13.1+ does not fix the issue for you

Just to check, we're saying this provider as of 3.41.0 no longer supports TF 0.12?

@slevenick
Copy link
Collaborator

@jamesyale good point. The tricky thing is that the cause of this issue was upgrading to the terraform-sdk v2: https://www.terraform.io/docs/extend/guides/v2-upgrade-guide.html

SDK v2 claims to work with 0.12.0+, but in this case that doesn't seem to be the case. I'll bring this up for discussion

@slevenick slevenick reopened this Oct 1, 2020
@slevenick
Copy link
Collaborator

I'm actually unable to reproduce this using 0.12.x

Are you able to get this error specifically when using 0.12? It seems like it was specific to 0.13.0

There is a similar looking issue around fields being removed, but that should be fixed by updating configs to use the correct field

@jamesyale
Copy link

jamesyale commented Oct 1, 2020

There is a similar looking issue around fields being removed, but that should be fixed by updating configs to use the correct field

Yep, you're right - I've got the wrong issue here and the one we're hitting is the same as #7381 where region is removed ala GoogleCloudPlatform/magic-modules#2436.

Thanks for looking into it!

@slevenick
Copy link
Collaborator

Great!

@ghost
Copy link

ghost commented Nov 1, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error πŸ€– πŸ™‰ , please reach out to my human friends πŸ‘‰ hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Nov 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants