Unable to deploy Firebase app using service account default credentials #1970
Comments
|
Same thing happening today on a Cloud Build environment with the correct IAM roles to deploy to Firebase Hosting. |
miumiu0917
changed the title
miumiu0917
changed the title
|
@miumiu0917 and @diogoterremoto this looks very similar to this issue: It looks like a Cloud Build issue to me, you're getting a 404 from an OAuth endpoint which implies some sort of network issue inside the container. As you can see in the stack trace the 404 happens with Have you tried reporting this issue to Cloud Build directly? |
|
We are suffering from this same issue (unable to use firebase-tools cli on google cloud build). I am still investigating but could this be causes by the deprecation of the GCP metadata endpoints? https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server#supported-google-libraries This requires GCP auth related libraries to be updated and the version of The page about the metadata server deprecation lists a number of nodejs libraries that need updating. It seems like at least |
|
@wvanderdeijl I think that might be it! I will dig into it, thank you for that. |
|
Thanks for the quick response. In the meanwhile I am trying to create my own workaround as we are currently unable to perform an important production deployment. |
|
Working on this in #1973 ... do you think you could try installing |
|
this only occurs on google cloud build (due to the metadata server usage). So a roundtrip to gcb for an attempt takes some time. Do you know the easiest way to install firebase-tools from your branch in a script on gcb? |
|
You should be able to do: |
|
Installing from git works fine locally, but it fails when running in the It seems like the I'll keep you posted |
|
@wvanderdeijl ah ok sorry about the issue there! You could also try this to install the |
|
I finally got it to work by not running the npm install as root as that will not completely run the This means I run the npm install with the non-privileged user Anyhow; the Should I keep this workaround in place or do you plan to release a new version with the fix very soon? |
|
@wvanderdeijl thanks for confirming! Depends on your definition of "soon". This fix seems simple and important so we can get a new version out early next week, but we can't get it out today (we don't release on Fridays). |
|
Thanks for the update. I am already very impressed with the very quick response times. I understand that releasing a new version on a friday as a "one man job" is not the best idea in the world. Thanks again! |
|
We had the same issue with our deployments and it is resolved by using branch mentioned 👍 A bit funny this "update" that made the old library not working anymore happened on Valentine's Day... where was the love? 😄 ❤️ |
|
The fix for this bug has been released in version |
|
Sorry for the basic q - we've been facing the same error on the deploy step on cloudbuild (last successful deploy was Feb 13th). I've updated firebase tools on my machine - but that doesnt seem to fix it on cloudbuild. How does one update the firebase tools version on cloudbuild |
|
@rajivsubra1981 Had the same issue, solved by rebuilding docker image for firebase community builder from here https://github.com/GoogleCloudPlatform/cloud-builders-community/tree/master/firebase, just follow the instruction in the root project readme. Once it was uploaded I also deleted the old image and everything worked fine. , |
|
@crtag Thank you! I ran |
|
@samtstern |
[REQUIRED] Environment info
firebase-tools: 7.13.0
Platform: Ubuntu on Cloudbuild
from cloud-builders-community
[REQUIRED] Test case
[REQUIRED] Steps to reproduce
firebase deploy[REQUIRED] Expected behavior
succesfully deployed.
[REQUIRED] Actual behavior
The text was updated successfully, but these errors were encountered: