Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment fails with "Not Found" error #82

Closed
rdev opened this issue Aug 24, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@rdev
Copy link

commented Aug 24, 2017

When trying to deploy I get this:

Error --------------------------------------------------

  Error: Not Found

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Stack Trace --------------------------------------------

Error: Error: Not Found
    at filArgs.reduce (node_modules/serverless-google-cloudfunctions/provider/googleProvider.js:67:33)
    at JWT.OAuth2Client._postRequest (/node_modules/google-auth-library/lib/auth/oauth2client.js:402:3)
    at postRequestCb (node_modules/google-auth-library/lib/auth/oauth2client.js:362:12)
    at Request._callback (node_modules/google-auth-library/lib/transporters.js:106:7)
    at Request.self.callback (node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request.<anonymous> (node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage.<anonymous> (node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:293:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:188:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickDomainCallback (internal/process/next_tick.js:128:9)
From previous event:
    at PluginManager.invoke (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/classes/PluginManager.js:242:22)
    at PluginManager.run (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/classes/PluginManager.js:261:17)
    at variables.populateService.then (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/Serverless.js:99:33)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)
From previous event:
    at Serverless.run (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/lib/Serverless.js:86:74)
    at serverless.init.then (.nvm/versions/node/v7.7.2/lib/node_modules/serverless/bin/serverless:39:50)
@pmuens

This comment has been minimized.

Copy link
Member

commented Aug 25, 2017

Thanks for opening @fivepointseven 👍

🤔 it looks like this is related to the APIs the Google plugin talks to (see here).

Have you followed the setup process here and enabled all the necessary APIs?

@pmuens pmuens added the bug label Aug 25, 2017

@rdev

This comment has been minimized.

Copy link
Author

commented Aug 25, 2017

@pmuens yes, I did. In fact this was a second deployment.
Also, when I rename service in serverless.yml to something different, it works

Edit:
Also (and I'm not sure if this is relevant to this bug) when I did it, Serverless started to ignore my specified bucket and puts functions into it's own with that autogenerated long name.

@pmuens

This comment has been minimized.

Copy link
Member

commented Aug 25, 2017

Thanks for getting back @fivepointseven 👍

That sounds like there's a problem in Googles end. Google Cloud Functions is still beta and I personally had some related experiences when working on this plugin...

Glad to hear that this doesn't prevent you from deploying altogether.

@rdev

This comment has been minimized.

Copy link
Author

commented Aug 25, 2017

The weird thing is, when I change the service to the one that doesn't deploy, I can still deploy fine using gcloud.
I'll poke around on weekend and see if I can find the root of the problem

@pmuens

This comment has been minimized.

Copy link
Member

commented Aug 25, 2017

The weird thing is, when I change the service to the one that doesn't deploy, I can still deploy fine using gcloud.

Hmm. Interesting!

I'll poke around on weekend and see if I can find the root of the problem

That would be super helpful @fivepointseven 💪!

Feel free to ping here if you need any help with that or have smth. to share 👍

@rdev

This comment has been minimized.

Copy link
Author

commented Aug 31, 2017

@pmuens I figured it out. The problem was indeed on Google's side.
I went to Cloud Console > Deployment Manager, deleted all deployments created by Serverless and deleted respective storage buckets and deployment with previously failing service name ran successfully.

@rdev rdev closed this Aug 31, 2017

@pmuens

This comment has been minimized.

Copy link
Member

commented Aug 31, 2017

Great! Thanks for the response @fivepointseven 👍

Glad to hear that yo've resolved this issue!

@fgilio

This comment has been minimized.

Copy link

commented Jan 10, 2019

Thanks @rdev!!!! I was going crazy :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.