Open haarchri opened 6 months ago
Hi @haarchri,
I cannot reproduce the error permanently.
I saw the same error message for a short time when the Connection.servicenetworking
resource was first created, but I was able to create it successfully in my subsequent attempts.
NAME READY SYNCED EXTERNAL-NAME AGE
globaladdress.compute.gcp.upbound.io/test-sc-ft-ga1 True True test-sc-ft-ga1 14m
NAME READY SYNCED EXTERNAL-NAME AGE
network.compute.gcp.upbound.io/test-sc-ft-n1 True True test-sc-ft-n1 14m
NAME READY SYNCED EXTERNAL-NAME
AGE
connection.servicenetworking.gcp.upbound.io/test-sc-ft1 True True projects%2Fofficial-provider-testing%2Fglobal%2Fnetworks%2Ftest-sc-ft-n1:servicenetworking.goog
leapis.com 14m
connection.servicenetworking.gcp.upbound.io/test-sc-ft2 True True projects%2Fofficial-provider-testing%2Fglobal%2Fnetworks%2Ftest-sc-ft-n1:servicenetworking.goog
leapis.com 9m8s
connection.servicenetworking.gcp.upbound.io/test-sc-ft3 True True projects%2Fofficial-provider-testing%2Fglobal%2Fnetworks%2Ftest-sc-ft-n1:servicenetworking.goog
leapis.com 7m14s
status:
atProvider:
id: projects%2Fofficial-provider-testing%2Fglobal%2Fnetworks%2Ftest-sc-ft-n1:servicenetworking.googleapis.com
network: projects/official-provider-testing/global/networks/test-sc-ft-n1
peering: servicenetworking-googleapis-com
reservedPeeringRanges:
- test-sc-ft-ga1
service: servicenetworking.googleapis.com
conditions:
- lastTransitionTime: "2024-03-11T23:30:31Z"
reason: ReconcileSuccess
status: "True"
type: Synced
- lastTransitionTime: "2024-03-11T23:32:25Z"
reason: Available
status: "True"
type: Ready
- lastTransitionTime: "2024-03-11T23:32:21Z"
reason: Success
status: "True"
type: LastAsyncOperation
- lastTransitionTime: "2024-03-11T23:39:49Z"
reason: UpToDate
status: "True"
type: Test
But there is a related issue upstream: https://github.com/hashicorp/terraform-provider-google/issues/16697
i have no luck with https://github.com/upbound/configuration-gcp-database/actions/runs/8235303142 - possible that i miss something
looks like its related to:
Update: resolved the issue by changing the name of the VPC I was trying to create and deploy.
In terraform resource "google_compute_network" I changed the 'name' element by one character. And now resource "google_service_networking_connection" applies onto that VPC with no problem.
It seems something with the VPC name conflicted in the backend. Maybe I deleted a VPC with that same name a few years ago?
did the same and create a never used VPC - now its working
but we hitting this issue during deletion: https://github.com/hashicorp/terraform-provider-google/issues/16275
after deletion in a fresh vpc same issue again:
Message: async create failed: failed to create the resource: [{0 Error waiting for Create Service Networking Connection: Error code 9, message: Cannot modify allocated ranges in CreateConnection. Please use UpdateConnection.
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
/fresh
Is there an existing issue for this?
Affected Resource(s)
Resource MRs required to reproduce the bug
No response
Steps to Reproduce
What happened?
after upgrade to v1.0.0 we get the following error from provider:
async create failed: failed to create the resource: [***0 Error waiting for Create Service Networking Connection: Error code 9, message: Cannot modify allocated ranges in CreateConnection. Please use UpdateConnection.
Relevant Error Output Snippet
No response
Crossplane Version
v1.15.0
Provider Version
v1.0.0
Kubernetes Version
No response
Kubernetes Distribution
No response
Additional Info
No response