Firebase Deploy --only Functions stuck at: functions: generating the service identity for eventarc.googleapis.com...

[itismejy]

Related issues

[REQUIRED] Version info

node:
v23.3.0

firebase-functions:
6.2.0
firebase-tools:
13.27.0

firebase-admin:
12.7.0

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

firebase deploy --only functions

[REQUIRED] Expected behavior

[REQUIRED] Actual behavior

Stuck here:
i functions: generating the service identity for pubsub.googleapis.com...
i functions: generating the service identity for eventarc.googleapis.com...

Were you able to successfully deploy your functions?

NO

None

When running with --debug:
[2024-12-28T06:18:23.977Z] <<< [apiv2][body] POST https://cloudfunctions.googleapis.com/v2/projects/messengerai-2500f/locations/us-central1/functions:generateUploadUrl {"uploadUrl":"https://storage.googleapis.com/gcf-v2-uploads-385863683187.us-central1.cloudfunctions.appspot.com/b0492521-0ed1-4545-8598-51fe4a993fd2.zip?GoogleAccessId=service-385863683187@gcf-admin-robot.iam.gserviceaccount.com&Expires=1735368503&Signature=IF09bgEhpzMjQ%2FsB0O9%2FPLplesgYbkVXu76RYfBzgYprStE4sRCQGFsW%2F1FuMAzU3R25fxhPgUfuxKHM7hVx3cRql4SCh8T9hqfW3B8GWoG8VsvTCoqEz9XcGqDE9cGKyryx7bzNWMv4Lrill8x1lwJuzQkLY2jzXso0ECCG8rqL8uM88ORvNnGMWKg62LAbj5sf5UJe3SgS8aQR8mxdVZcSpWSJOukkpyx82ROOfiVgyO4KojD3M77zRQvoj7uwaAf%2B%2BehB8C2WW01I5MAUGHox6J6K2z4Aq9xJhNY4UZhhsUEhvjREhDQFiKQG5T8c14fcs%2B2FhMQKbQP4LOT5rw%3D%3D","storageSource":{"bucket":"gcf-v2-uploads-385863683187.us-central1.cloudfunctions.appspot.com","object":"b0492521-0ed1-4545-8598-51fe4a993fd2.zip"}}
[2024-12-28T06:18:23.978Z] >>> [apiv2][query] PUT https://storage.googleapis.com/gcf-v2-uploads-385863683187.us-central1.cloudfunctions.appspot.com/b0492521-0ed1-4545-8598-51fe4a993fd2.zip GoogleAccessId=service-385863683187%40gcf-admin-robot.iam.gserviceaccount.com&Expires=1735368503&Signature=IF09bgEhpzMjQ%2FsB0O9%2FPLplesgYbkVXu76RYfBzgYprStE4sRCQGFsW%2F1FuMAzU3R25fxhPgUfuxKHM7hVx3cRql4SCh8T9hqfW3B8GWoG8VsvTCoqEz9XcGqDE9cGKyryx7bzNWMv4Lrill8x1lwJuzQkLY2jzXso0ECCG8rqL8uM88ORvNnGMWKg62LAbj5sf5UJe3SgS8aQR8mxdVZcSpWSJOukkpyx82ROOfiVgyO4KojD3M77zRQvoj7uwaAf%2B%2BehB8C2WW01I5MAUGHox6J6K2z4Aq9xJhNY4UZhhsUEhvjREhDQFiKQG5T8c14fcs%2B2FhMQKbQP4LOT5rw%3D%3D
[2024-12-28T06:18:23.979Z] >>> [apiv2][body] PUT https://storage.googleapis.com/gcf-v2-uploads-385863683187.us-central1.cloudfunctions.appspot.com/b0492521-0ed1-4545-8598-51fe4a993fd2.zip [stream]

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not have all the information required by the template. Looks like you forgot to fill out some sections. Please update the issue with more information.

[aalej]

Hey @itismejy, sorry to hear you encountered this issue. I'm working on reproducing this but so far, when I tried deploying functions the deployment finishes successfully.

A couple of questions and suggestions to help us get a better idea of what could be causing this:

• Try connecting to a different network, and temporarily disable any VPN or Firewall you may have. This is to rule out the possibility that this is a network related issue.
• What functions are you deploying? Could you share some code snippets?
• Are the deployments sometimes successful, or does it always get stuck?
• IIRC, if an API request takes too long to complete then the CLI should timeout and raise an error. If you wait a couple of minutes, are any errors being raised or is the CLI just stuck deploying?

[google-oss-bot]

Hey @itismejy. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@itismejy if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.