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

Resource still contains unknown values during apply #25117

Open
ovadbar opened this issue Jun 3, 2020 · 6 comments
Open

Resource still contains unknown values during apply #25117

ovadbar opened this issue Jun 3, 2020 · 6 comments
Labels
bug core waiting for reproduction unable to reproduce issue without further information

Comments

@ovadbar
Copy link

ovadbar commented Jun 3, 2020

Terraform Version

12.16? Terraform docker latest as of now

...
### Terraform Configuration Files
resource "google_dns_record_set" "zones" {
  name         = "${var.config["sbc"]["kamailio_tls_domain"]}."
  type         = "A"
  ttl          = 300
  managed_zone = var.dns_zone
  rrdatas      = [module.sbc.0.public_ip]
}

Debug Output

Too much output to paste

Crash Output

Error: configuration for module.iac_gcp.google_dns_record_set.zones still contains unknown values during apply (this is a bug in Terraform; please report it!)

Expected Behavior

Resource. created

Actual Behavior

Error: configuration for module.iac_gcp.google_dns_record_set.zones still contains unknown values during apply (this is a bug in Terraform; please report it!)

Steps to Reproduce

  1. terraform init
  2. terraform apply

Additional Context

terraform running in a a gitlab pipeline

References

@danieldreier
Copy link
Contributor

Hi! Thanks for reporting this. Based on the error message you're showing I think this is probably a valid issue, and I'd like to reproduce it locally.

To do that, I have to be able to run this and run it on my workstation without inventing any details in order to be confident we're seeing the same behavior. As-is, this is an incomplete reproduction case, and so I'm stuck.

I put the example you provided in https://github.com/danieldreier/terraform-issue-reproductions/blob/master/25117/25117.tf as a starting point. I do have a GCP account I can test from, so if you can make a PR to get this to where I can run it I'd be happy to try and reproduce on my end.

@danieldreier danieldreier added the waiting-response An issue/pull request is waiting for a response from the community label Jun 15, 2020
@ovadbar
Copy link
Author

ovadbar commented Jun 15, 2020 via email

@ghost ghost removed the waiting-response An issue/pull request is waiting for a response from the community label Jun 15, 2020
@danieldreier
Copy link
Contributor

Thank you @ovadbar! I appreciate that. I know that simplifying these sort of issue reproduction cases can be difficult, but it's also the only way we can reproduce it on our end. If you think it's hard to simplify to a good reproduction case on your end, imagine how tough it is on our side without even having the starting point of your codebase! I appreciate your help in reporting it and trying to simplify the reproduction case!

@danieldreier danieldreier added the waiting-response An issue/pull request is waiting for a response from the community label Jun 15, 2020
@ovadbar
Copy link
Author

ovadbar commented Jun 16, 2020 via email

@ghost ghost removed waiting-response An issue/pull request is waiting for a response from the community labels Jun 16, 2020
@ovadbar
Copy link
Author

ovadbar commented Jun 16, 2020 via email

@queglay
Copy link

queglay commented Aug 22, 2020

I'm getting this errors if I deploy resources, and then roll them back (like disabling a vpc), but still keeping some null resources

@alisdair alisdair added the waiting for reproduction unable to reproduce issue without further information label Sep 18, 2020
@jbardin jbardin removed the v0.12 label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug core waiting for reproduction unable to reproduce issue without further information
Projects
None yet
Development

No branches or pull requests

6 participants