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

terraforming-gcp fails on Terraform v0.11.13 #3377

Closed
ghost opened this issue Apr 3, 2019 · 3 comments
Closed

terraforming-gcp fails on Terraform v0.11.13 #3377

ghost opened this issue Apr 3, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 3, 2019

This issue was originally opened by @amcginlay as hashicorp/terraform#20922. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.11.13

Terraform Configuration Files

This config

https://github.com/pivotal-cf/terraforming-gcp/releases/tag/v0.74.0

With terraform.tfvars file as follows created inside the unpacked terraforming_pas directory:

dns_suffix             = "mydomain.com"
env_name               = "subdomain"
region                 = "us-central1"
zones                  = ["us-central1-b", "us-central1-a", "us-central1-c"]
project                = "my-project-id"
opsman_image_url       = ""
opsman_vm              = 0
create_gcs_buckets     = "false"
external_database      = 0
isolation_segment      = 0
service_account_key = <<SERVICE_ACCOUNT_KEY
<GCP_CREDENTIALS_JSON_HERE>
SERVICE_ACCOUNT_KEY

Crash Output

https://gist.github.com/amcginlay/167b2f8442e0de6b01f8218347116f97

Expected Behavior

It should have deployed the infrastructure for the Pivotal Application Service

Actual Behavior

It failed as per the crash report

Steps to Reproduce

terraform init
terraform apply --auto-approve
@amcginlay
Copy link

Weirdly, this issue has proven stubbornly difficult to reproduce.
Feel free to close this issue.

@rileykarson
Copy link
Collaborator

Sounds good! The error looks similar to some other issues we've had, upgrading to a 2.X series release of the Google provider should help if you encounter this again.

@ghost
Copy link
Author

ghost commented May 5, 2019

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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants