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

CloudSQL change of VPC and google_dns_record_set => Provider produced inconsistent final plan #10131

Closed
tpoindessous opened this issue Sep 22, 2021 · 6 comments
Assignees
Labels

Comments

@tpoindessous
Copy link
Contributor

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.12.31
+ provider.google v3.65.0
+ provider.random v3.1.0

Affected Resource(s)

  • google_sql_database_instance
  • google_dns_record_set

Terraform Configuration Files

Debug Output

Error: Provider produced inconsistent final plan
When expanding the plan for google_dns_record_set.record to include new values
learned so far during apply, provider "registry.terraform.io/-/google"
produced an invalid new value for .rrdatas[0]: was
cty.StringVal("10.111.38.4"), but now cty.StringVal("10.5.176.4").
This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Panic Output

Expected Behavior

  • google_dns_record_set is set to new IP address.

Actual Behavior

  • TF exits with an error.

Steps to Reproduce

  1. terraform apply on a google_sql_database_instance with a private IP and a google_dns_record_set which uses this private IP.
  2. Changes TF code to use another VPC for private IP. google_sql_database_instance will change its private IP.
  3. TF exits with a error

Important Factoids

References

Thanks !

@edwardmedia edwardmedia self-assigned this Sep 22, 2021
@edwardmedia
Copy link
Contributor

@tpoindessous can you share your config and its execution debug log? Thanks

@edwardmedia
Copy link
Contributor

@tpoindessous is this still an issue?

@tpoindessous
Copy link
Contributor Author

Hi @edwardmedia , yes, this is still an issue.

I can't give you the execution debug log but I will give you the config. If you really need the execution debug log, I can start a lab project and try to reproduce it, but it will take time.

Thanks !

@edwardmedia
Copy link
Contributor

@tpoindessous let's get the config first

@edwardmedia
Copy link
Contributor

@tpoindessous closing this issue now. Please reopen once you have the config. Thanks

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants