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
An error occurred: ApiGatewayDeploymentxxxxx - No integration defined for method - when v1.28 was used #5100
Comments
@densbozz the output references that you're still using v1.27.3. That rules out the newer version as a probable cause. |
@densbozz @drexler I was experiencing the same issue, the exact same error output and resources missing the OPTIONS method. It appears to be related to a change in 1.28.0, because when deploying after the switch there are create method events being output in the event log despite no changes to my configuration. It seems like serverless was attempting to create OPTIONS methods that were already existent. I was able to resolve it by removing If this doesn't work and the problem is being more persistent, I was able to resolve the issue on one of my service's stages by removing all lambdas with http events (alternatively you can fully remove the service) from your serverless config, deploying, replacing, and deploying once again. |
@mitchelljfs - thanks for the response. this makes sense now. can you confirm the workaround you did is just one time, and your succeeding serverless deployments have been successful? |
@densbozz no problem. I have not run into the problem more than once per stage, after using one of the two methods I described. So, yes. |
We're also experiencing this issue. The workaround is less than ideal, so hopefully this'll be resolved in 1.28.1 |
simply removing What solved it for me was deleting all my http events (except for one test event so that an API Gateway deployment would still be created), deploying, restoring all http events, deploying again. NOTE: It appears this completely re-creates the Lambda function instead of just updating it as all settings (environment variables, VPCs, roles, etc) were lost, which doesn't happen on a normal deploy. |
Hey @densbozz @drexler @mitchelljfs @dschep and @skylarmb! So I tried to reproduce this today with the following (super simple) service: service: regression
provider:
name: aws
runtime: nodejs6.10
functions:
hello:
handler: handler.hello
events:
- http:
path: test
method: POST
cors: true I started with a deployment via Can anyone of you share a simple (redacted) |
@pmuens here is a redacted version of our
|
We just updated from version 1.26.1 (pretty old...) to version 1.30.1 and we just this same problem with our http event driven lambdas... This happens when attempting to create the web hook: |
We tried redeploying with cors=true commented and then redeploying uncommenting it again in our lambdas and it worked... in case you guys are wondering if the workaround works. It worked for us at least in some of our lambdas, still need to try it in all our others. Will report here if we experience something different. Thanks |
Hey everyone! We think we finally figured out why this happens. We've provided a fix via #5256 and test it thoroughly right now. |
Hey everyone! This issue has been fixed via #5256 and is now available in v1.30.3. |
Hi Everyone, We run into the same issue first time today with v1.32.0, we do an update to v1.33.1 and the issue is still there. It does not work for us by commenting all "cors" trick. Here is our log: Serverless Error --------------------------------------- An error occurred: ApiGatewayDeployment1542460698067 - No integration defined for method (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: 55678d9d-ea6b-11e8-b095-5f8066d9233c). Get Support -------------------------------------------- Your Environment Information ----------------------------- |
Sorry folks. This is a false alarm and does not related serverless framework. |
Thanks for following up with the root cause of your issue @shevaul |
Hi All , |
Hi all, facing the same issue setting cors. |
+1 |
I had to remove the CloudFormation Stack and deploy it again. :/ |
My team started seeing this error today using serverless 1.51.0 . |
I faced the same error when I created API Gateway resourses with both Cloudformation and by manually using the Amazon console. |
I am facing the same issue with |
So strange, I had to delete the stack and created a new one with the exact same config and it worked. Not sure if it is an issue with serverless, could be something with aws as well |
This is a (Bug Report)
This error started July 4 and coincidentally 1.28.0 was released.
our CodeBuild is failing since then.
In our CodeBuild spec...
------------------------ code build spec ---------------
version: 0.2
phases:
install:
commands:
- ls -a
- npm install -g serverless
build:
commands:
- npm install --only=dev
post_build:
commands:
- serverless deploy --stage $APP_DEPLOYMENT_ENVIRONMENT --package serverless
Description
For bug reports:
Additional Data - Error Stack in Code Build
Serverless: Checking Stack update progress...
....................................................................................................................................
Serverless: Operation failed!
Serverless Error ---------------------------------------
An error occurred: ApiGatewayDeploymentxxxxxxx - No integration defined for method (Service: AmazonApiGateway; Status Code: 400; Error Code: BadRequestException; Request ID: xxxxxxxxxxxxxxxxxxx).
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information -----------------------------
OS: linux
Node Version: 6.3.1
Serverless Version: 1.27.3
[Container] 2018/07/06 04:46:55 Command did not exit successfully serverless deploy --stage $APP_DEPLOYMENT_ENVIRONMENT --package serverless exit status 1
[Container] 2018/07/06 04:46:55 Phase complete: POST_BUILD Success: false
[Container] 2018/07/06 04:46:55 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: serverless deploy --stage $APP_DEPLOYMENT_ENVIRONMENT --package serverless. Reason: exit status 1
The text was updated successfully, but these errors were encountered: