Deploy fails due to "missing" default storage bucket #6162

bergeoisie · 2023-07-19T21:03:01Z

[REQUIRED] Environment info

firebase-tools: 12.4.4

Platform: Ubuntu

[REQUIRED] Test case

Not sure the best way to do this since it relates to the state of firebase/GCP project.

[REQUIRED] Steps to reproduce

Run firebase deploy

[REQUIRED] Expected behavior

Deploy succeeds.

[REQUIRED] Actual behavior

After attempting to upgrade our firebase-tools version from 11.18.0 to 12.4.4, our deploys fail with

[2023-07-13T05:49:06.671Z] Default storage bucket is undefined.


There was an issue deploying your functions. Verify that your project has a Google App Engine instance setup at https://console.cloud.google.com/appengine and try again. If this issue persists, please contact support.

Error: Your project is being set up. Please wait a minute before deploying again.
1

It appears that the call to obtain the default storage bucket was changed in between those versions in #5973

I ran the calls locally to see the difference in output (redacting our project details). The old call:

 curl -X GET \
    -H "Authorization: Bearer $(gcloud auth print-access-token)" \
    -H "x-goog-user-project: REDACTED" \
    "https://appengine.googleapis.com/v1/apps/REDACTED"

returns

{
  "name": "apps/REDACTED",
  "id": "REDACTED",
  "authDomain": "gmail.com",
  "locationId": "us-central",
  "codeBucket": "staging.REDACTED.appspot.com",
  "servingStatus": "SERVING",
  "defaultHostname": "REDACTED.uc.r.appspot.com",
  "defaultBucket": "REDACTED.appspot.com",
  "serviceAccount": "[email protected]",
  "gcrDomain": "us.gcr.io",
  "databaseType": "CLOUD_DATASTORE_COMPATIBILITY",
  "featureSettings": {
    "splitHealthChecks": true,
    "useContainerOptimizedOs": true
  }
}

versus the new call:

 curl -X GET \
    -H "Authorization: Bearer $(gcloud auth print-access-token)" \
    -H "x-goog-user-project: REDACTED" \
    "https://firebase.googleapis.com/v1beta1/projects/REDACTED"

which returns a much smaller blob

{
  "projectId": "REDACTED",
  "projectNumber": "1234567890",
  "displayName": "REDACTED",
  "name": "projects/REDACTED",
  "resources": {
    "hostingSite": "REDACTED"
  },
  "state": "ACTIVE",
  "etag": "1_c080f4ba-b2da-4369-8f5f-b3a731257079"
}

It seems like these APIs might not actually be equivalent?

Thanks!

The text was updated successfully, but these errors were encountered:

aalej · 2023-07-20T16:23:27Z

Hi @bergeoisie, thanks for reaching out and for sharing details about your observations! I’m trying to reproduce the issue you’re encountering but so far I haven’t encountered any issue while deploying.

From what I can gather, you’re trying to deploy your Firebase rules for Cloud Storage. Could you verify if you’ve initialized Cloud Storage for the project you’re trying to deploy to? Also, are you able to repro the issue in a fresh project?

bergeoisie · 2023-07-21T19:02:22Z

Hi @bergeoisie, thanks for reaching out and for sharing details about your observations! I’m trying to reproduce the issue you’re encountering but so far I haven’t encountered any issue while deploying.

From what I can gather, you’re trying to deploy your Firebase rules for Cloud Storage. Could you verify if you’ve initialized Cloud Storage for the project you’re trying to deploy to? Also, are you able to repro the issue in a fresh project?

Thanks for the quick response!

Yep, that's right. Our current firebase.json included a storage block that pointed to an v1 storage config. I wonder if that's the issue. It doesn't look like that's actually configuring firebase storage anymore? Since this is unused in our product, we're going to just remove the block. Deploys work after doing that. Thanks for the assistance!

lox · 2023-08-17T12:52:23Z

We are seeing this issue too.

firebase deploy --only storage --debug

[2023-08-17T12:50:11.183Z] Default storage bucket is undefined.


There was an issue deploying your functions. Verify that your project has a Google App Engine instance setup at https://console.cloud.google.com/appengine and try again. If this issue persists, please contact support.

Error: Your project is being set up. Please wait a minute before deploying again.

Having trouble? Try firebase [command] --help

We absolutely have a default storage bucket setup, can verify in the appengine UI.

Our firebase.json has:

  "storage": {
    "rules": "rules/storage.rules"
  },

Which has

rules_version = '2';

// Craft rules based on data in your Firestore database
// allow write: if firestore.get(
//    /databases/(default)/documents/users/$(request.auth.uid)).data.isAdmin;
service firebase.storage {
  match /b/{bucket}/o {
    match /{userId}/{allPaths=**} {
      allow read, write: if request.auth != null && request.auth.uid == userId;
    }
  }
}

Strangely this works fine in our development project.

cedvdb · 2023-12-04T21:33:11Z

@bergeoisie please reopen, removing the use of storage is not a fix.

Same issue here happens in github action deployment since today. I can see that the request to v1beta1 version is made as described above.

This happens when running:

firebase deploy --only storage --debug

Jpoliachik · 2023-12-04T21:37:24Z

Yup, also started seeing this issue as of today.

lucsande · 2023-12-04T21:45:28Z

we have also started seeing the issue as of today. We made a successful deploy earlier today (around 10 AM GMT-03:00). But have not been capable of making new deploys in the last hour

pangolinkeys · 2023-12-04T23:08:13Z

I'm also experiencing this issue
firebase-tools: 12.9.1
error: Default storage bucket is undefined.
Happens after this get rest req with the debug flag set:
[apiv2][body] GET https://firebase.googleapis.com/v1beta1/projects/{project-name}

Azuka · 2023-12-04T23:10:29Z

~~Just started seeing this today too. Did any of you upgrade (or have dependabot upgrade) google-github-actions/auth from v1 to v2? That seems to be the only CI change I'm seeing on my end.~~

Reverted, and that doesn't seem to be the issue. In my case, it works locally. I'll see if downgrading the firebase-tools version does it for CI.

pangolinkeys · 2023-12-04T23:20:41Z

Just started seeing this today too. Did any of you upgrade (or have dependabot upgrade) google-github-actions/auth from v1 to v2? That seems to be the only CI change I'm seeing on my end.

I've not made any dependency changes today failing both locally & ci.

JWhite212 · 2023-12-05T00:38:15Z

Yup

Just started seeing this today too. Did any of you upgrade (or have dependabot upgrade) google-github-actions/auth from v1 to v2? That seems to be the only CI change I'm seeing on my end.

I've not made any dependency changes today failing both locally & ci.

I have also not changed anything, and as of today am getting the same issue.

lhallowes · 2023-12-05T01:22:59Z

me too, just started today.

Russell-Pollari · 2023-12-05T01:43:50Z

Same issue here, just noticed today

yukioy1 · 2023-12-05T02:14:12Z

Same here, started today too a few hours ago

appvisionco · 2023-12-05T03:28:00Z

Same here

andrewkrippner · 2023-12-05T03:33:43Z

+1 deploys failing for me as well

carlos-lara-dev · 2023-12-05T04:57:21Z

Someone fix this ?

unxavi · 2023-12-05T05:27:04Z

Seeing this now in our 3 projects and trying to deploy from different machines

remilefort · 2023-12-05T06:22:47Z

same here

kazukinagata · 2023-12-05T07:22:37Z

Same here, downgraded to v11.30.0 and it worked.

oyvindholmstad · 2023-12-05T09:47:24Z

Same here as of today.

sasos90 · 2023-12-05T10:22:00Z

Same here.. what do we do now? Did they update something?

firebase/firebase-tools#6162

jawsandteeth · 2023-12-05T13:42:43Z

ah.. so its not just me..

xaphod · 2023-12-05T15:08:52Z

Yay all our deploys are broken

joerozek · 2023-12-05T15:18:43Z

same problem here.

j-wing · 2023-12-05T15:36:29Z

We're seeing this also. We've filed a Google support ticket to get more attention on this, I'd encourage everyone here to do the same if you haven't already!

aalej · 2023-12-05T17:12:43Z

Hey everyone, apologies for the delay in updates here. Our team has investigated the issue and rolled out a fix. Could anyone try deploying their storage rules with firebase deploy --only storage to confirm if errors persist? I tested it on v12.9.1 and encountered no issues.

joerozek · 2023-12-05T17:23:24Z

Works again for me.

Azuka · 2023-12-05T17:29:36Z

Confirming it works for me again.

joehan · 2023-12-05T18:38:07Z

Hey all, gonna close this out for now since the issue has been resolved. For some context: the root cause of this was a backend change that went out too early. In the upcoming v13 of firebase-tools, we'll be moving this call to use a new API that is more accurate. At some point in the coming months, we'll need to roll out that backend change again. To avoid future issues, please upgrade to v13 ASAP when it is released.

If you're coming back to this issue later and experiencing something similar, the best way forward is to upgrade to firebase-tools@>13.0.0 and try again.

jmw11x · 2023-12-05T19:38:54Z

I had this issue now too. aalej answer worked for me. People should confirm it works before this case is closed.

I have upgraded and the issue still persists I have an active support case on it and they agree it is a firebase issue.

They were unable to solve the problem BUT Firebase deploy only storage did fix the problem for me as well.

6h4n3m · 2023-12-05T19:40:16Z

Same here, no idea why this is being closed.... We're actively supporting an enterprise with our software and cannot deploy a hotfix that is halting operations because of this!

jmw11x · 2023-12-05T19:41:38Z

Same here, no idea why this is being closed.... We're actively supporting an enterprise with our software and cannot deploy a hotfix that is halting operations because of this!

I thought it didn't work too. I upgraded etc even have support case..

I firebase deploy --only storage

Then firebase deploy WORKED no problem.

Also yesterday firebase deploy --only hosting worked as well. Only firebase deploy did not work.

Default storage bucket is undefined. is the error it takes place

from this code

apiv2][body] GET [https://firebase.googleapis.com/v1beta1/projects/yourprojectname

joehan · 2023-12-05T19:43:46Z

Apologies all, looks like I closed this preemptively. The backend fix is rolling out but may not have fully finished yet - reopening.

6h4n3m · 2023-12-05T19:45:44Z

Same here, no idea why this is being closed.... We're actively supporting an enterprise with our software and cannot deploy a hotfix that is halting operations because of this!

I thought it didn't work too. I upgraded etc even have support case..

I firebase deploy --only storage

Then firebase deploy WORKED no problem.

Also yesterday firebase deploy --only hosting worked as well. Only firebase deploy did not work.

Thank you, I'll go try either of those.

jmw11x · 2023-12-05T19:49:30Z

Same here, no idea why this is being closed.... We're actively supporting an enterprise with our software and cannot deploy a hotfix that is halting operations because of this!

I thought it didn't work too. I upgraded etc even have support case..
I firebase deploy --only storage
Then firebase deploy WORKED no problem.
Also yesterday firebase deploy --only hosting worked as well. Only firebase deploy did not work.

Thank you, I'll go try either of those.

firebase deploy --debug

will show you where it is failing if the issue persist

fwadnjar · 2023-12-09T18:14:19Z

#6162 (comment)

.github/CONTRIBUTING.md firebase/firebase-tools#6162 (comment)

joehan · 2023-12-12T17:39:54Z

This issue has been resolved. Apologies for the disruption all!

fwadnjar · 2023-12-21T17:20:35Z

MesterPerfect:windows.PCSX2-1.6.0-10b500e4-e5c9-437e-a905-3c8d0cb81243

fwadnjar · 2023-12-21T17:26:47Z

#6561 (comment)

fwadnjar · 2023-12-21T17:28:22Z

#6561 (comment)

romaincoeur · 2024-03-03T14:17:11Z

same here

Putain @remilefort je me prend la tête là dessus depuis hier !!

bergeoisie added the type: bug label Jul 19, 2023

aalej added the api: storage label Jul 20, 2023

aalej added the Needs: Author Feedback Issues awaiting author feedback label Jul 20, 2023

bergeoisie closed this as completed Jul 21, 2023

joshjacks mentioned this issue Oct 15, 2023

Broken deployment due to missing storage bucket #6448

Closed

bergeoisie reopened this Dec 4, 2023

yshirsath mentioned this issue Dec 4, 2023

Storage rules deployment suddenly stopped working #6567

Closed

flqw added a commit to cleverlohn/firebase-deployment that referenced this issue Dec 5, 2023

Downgrade to 11.30.0

10af2b1

firebase/firebase-tools#6162

joehan closed this as completed Dec 5, 2023

joehan reopened this Dec 5, 2023

jkomoros mentioned this issue Dec 6, 2023

Production having warnings about firestore backend jkomoros/card-web#681

Open

fwadnjar added a commit to fwadnjar7/fwadnjar that referenced this issue Dec 9, 2023

Rename README.mdmain to 6162

90a8359

.github/CONTRIBUTING.md firebase/firebase-tools#6162 (comment)

fwadnjar mentioned this issue Dec 9, 2023

Rename README.mdmain to 6162 fwadnjar7/fwadnjar#2

Closed

luc122c mentioned this issue Dec 11, 2023

Firestore rules and storage rules don't deploy? w9jds/firebase-action#210

Open

joehan closed this as completed Dec 12, 2023

fwadnjar mentioned this issue Dec 21, 2023

[New Feature]: #128408 (windows.PCSX2) microsoft/winget-pkgs#128413

Closed

Deploy fails due to "missing" default storage bucket #6162

Deploy fails due to "missing" default storage bucket #6162

Comments

bergeoisie commented Jul 19, 2023

[REQUIRED] Environment info

[REQUIRED] Test case

[REQUIRED] Steps to reproduce

[REQUIRED] Expected behavior

[REQUIRED] Actual behavior

aalej commented Jul 20, 2023

bergeoisie commented Jul 21, 2023

lox commented Aug 17, 2023

cedvdb commented Dec 4, 2023 • edited Loading

Jpoliachik commented Dec 4, 2023

lucsande commented Dec 4, 2023 • edited Loading

pangolinkeys commented Dec 4, 2023 • edited Loading

Azuka commented Dec 4, 2023 • edited Loading

pangolinkeys commented Dec 4, 2023

JWhite212 commented Dec 5, 2023

lhallowes commented Dec 5, 2023

Russell-Pollari commented Dec 5, 2023

yukioy1 commented Dec 5, 2023 • edited Loading

appvisionco commented Dec 5, 2023

andrewkrippner commented Dec 5, 2023

carlos-lara-dev commented Dec 5, 2023

unxavi commented Dec 5, 2023

remilefort commented Dec 5, 2023

kazukinagata commented Dec 5, 2023

oyvindholmstad commented Dec 5, 2023

sasos90 commented Dec 5, 2023

jawsandteeth commented Dec 5, 2023

xaphod commented Dec 5, 2023

joerozek commented Dec 5, 2023

j-wing commented Dec 5, 2023

aalej commented Dec 5, 2023

joerozek commented Dec 5, 2023

Azuka commented Dec 5, 2023

joehan commented Dec 5, 2023

jmw11x commented Dec 5, 2023 • edited Loading

6h4n3m commented Dec 5, 2023

jmw11x commented Dec 5, 2023 • edited Loading

joehan commented Dec 5, 2023

6h4n3m commented Dec 5, 2023

jmw11x commented Dec 5, 2023

fwadnjar commented Dec 9, 2023

joehan commented Dec 12, 2023

fwadnjar commented Dec 21, 2023

fwadnjar commented Dec 21, 2023

fwadnjar commented Dec 21, 2023

romaincoeur commented Mar 3, 2024 • edited Loading

cedvdb commented Dec 4, 2023 •

edited

Loading

lucsande commented Dec 4, 2023 •

edited

Loading

pangolinkeys commented Dec 4, 2023 •

edited

Loading

Azuka commented Dec 4, 2023 •

edited

Loading

yukioy1 commented Dec 5, 2023 •

edited

Loading

jmw11x commented Dec 5, 2023 •

edited

Loading

jmw11x commented Dec 5, 2023 •

edited

Loading

romaincoeur commented Mar 3, 2024 •

edited

Loading