CODEWITHSUNDEEP
google-cloud-platformgoogle-cloud-rungoogle-cloud-networkinggoogle-vpc
Abdellatif Derbel
Abdellatif Derbel

Reputation: 604

Cloud run Instance failed to start because permission was denied when creating an address in the subnetwork

I have been using Direct VPC egress in google cloud run since May 2, 2024 to access to Cloud SQL via private IP in the same network. I have 2 environnments prod and staging, same configurations except min-instances (1 in prod and 0 in staging). Subnet range = 10.2.0.0/22

Since June 18 I have been receiving these errors (only in staging) when the number of instances remains 0 for more than 20 minutes. (Only for the first request, in other cases works well)

Instance failed to start because permission was denied when creating an address in the subnetwork, Please check IAM settings.

Even though I assigned the networkUser role to the cloud run service agent.

Upvotes: 2

Views: 519

Answers (1)

user25881671
user25881671

Reputation: 11

I've contacted GoogleCloud support.

The problem with PERMISSION_DENIED errors in the IP allocation of Serverless Direct VPC subnets appears to have been an error caused by a bug on the GoogleCloud side. The product team has now finished restoring the Direct VPC service so that it can be provisioned normally, and there is no possibility of a recurrence.


https://support.cloud.google.com/portal/system-status
(Cloud Run customers using Direct VPC egress may see intermittent failures with deploying new revisions and autoscaling)

Upvotes: 1

Related Questions