Creating multiple SQL instances with Private IP

[roger-rainey]

I am trying to use these modules to create cloud sql instances using terragrunt. I can get this module to create one instance but when it tries to create a second instance it will fail. It creates a new separate private network and then will fail with this error.

google_service_networking_connection.private_vpc_connection: Error waiting for Create Service Networking Connection: Error code 9, message: Cannot modify allocated ranges in CreateConnection. Please use UpdateConnection.

[one1zero1one]

@roger-rainey seen the same error, for me happened after I did couple of destroy/apply iterations. Looks like a GCP bug. What helped for me to get it unstuck was this thread , more precisely:

gcloud beta services vpc-peerings update \
    --service=servicenetworking.googleapis.com \
    --ranges=private-ip-address \
    --network=sandbox-net \
    --project=sandbox-XXXXX \
    --force

[roger-rainey]

Is there a gcloud command that can give the private ip address ranges?

On Thu, May 30, 2019 at 4:27 AM Daniel Radu notifications@github.com wrote:

@roger-rainey https://github.com/roger-rainey seen the same error, for me happened after I did couple of destroy/apply iterations. Looks like a GCP bug. What helped for me to get it unstuck was this thread https://github.com/terraform-providers/terraform-provider-google/issues/3294 , more precisely:

gcloud beta services vpc-peerings update \ --service=servicenetworking.googleapis.com \ --ranges=private-ip-address \ --network=sandbox-net \ --project=sandbox-XXXXX \ --force```

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gruntwork-io/terraform-google-sql/issues/36?email_source=notifications&email_token=AIJR57FXG64UWAOT3TLDLILPX622NA5CNFSM4HQVD6I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSCYTA#issuecomment-497298508, or mute the thread https://github.com/notifications/unsubscribe-auth/AIJR57BBD4BTSHRRIYHVLKTPX622NANCNFSM4HQVD6IQ .

[autero1]

Hi @roger-rainey Could you provide a bit more details on how you're trying to use the module? Note that the root of the repo is an example, and the module itself is in modules/cloud-sql and should be referenced with source = "git::git@github.com:gruntwork-io/terraform-google-sql.git//modules/cloud-sql?ref=vX.Y.Z". The network and peering creation are only part of the examples, the cloud-sql -module only creates database artifacts.

[autero1]

@roger-rainey It is indeed a GCP issue - we hit the same issue recently and the cure is to do as @one1zero1one suggested.

run the following command to get the peering ip:

gcloud compute addresses list --global --filter="purpose=VPC_PEERING" --project=your-project-id

Then, using the private ip, run this:

gcloud beta services vpc-peerings update \
    --service=servicenetworking.googleapis.com \
    --ranges=private-ip-address \
    --network=XXXXX \
    --project=sandbox-XXXXX \
    --force

[iniinikoski]

Hi,

Any idea is still bug still valid...? Looks like we've bumped into a similar case regarding Cloud SQL + peering when working on parallel SQLs...

[Etiene]

Apologies for the delay in responding to this issue. Please see below:

Sunset notice

We believe there is an opportunity to create a truly outstanding developer experience for deploying to the cloud, however developing this vision requires that we temporarily limit our focus to just one cloud. Gruntwork has hundreds of customers currently using AWS, so we have temporarily suspended our maintenance efforts on this repo. Once we have implemented and validated our vision for the developer experience on the cloud, we look forward to picking this up. In the meantime, you are welcome to use this code in accordance with the open source license, however we will not be responding to GitHub Issues or Pull Requests.

If you wish to be the maintainer for this project, we are open to considering that. Please contact us at support@gruntwork.io.

[eak12913]

Closing due to repo sunset