serverless/serverless

Deploy crashes randomly - ChangeSet lambdas-dev-change-set cannot be created due to a mismatch with existing attribute Template

Open

#11.649 aberto em 31 de dez. de 2022

Ver no GitHub
 (11 comments) (0 reactions) (1 assignee)JavaScript (46.915 stars) (5.734 forks)batch import
cat/deploymentcat/dxenhancementgood first issuehelp wanted

Description

Are you certain it's a bug?

  • Yes, it looks like a bug

Is the issue caused by a plugin?

  • It is not a plugin issue

Are you using the latest v3 release?

  • Yes, I'm using the latest v3 release

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Issue description

Every 5 or so deploys, I get this error:

Deploying lambdas to stage dev (ap-northeast-1, "default" provider)
Compiling to node16 bundle with esbuild...
Compiling with concurrency: Infinity
Compiling completed.
Zip function: prompt-next-process - 1.11 MB [121 ms]
Zip function: prompt-scheduled-process - 1.11 MB [122 ms]
Uploading CloudFormation file to S3
Uploading State file to S3
Uploading service prompt-next-process.zip file to S3 (1.36 MB)
Uploading service prompt-scheduled-process.zip file to S3 (1.36 MB)
Creating new change set
× Stack lambdas-dev failed to deploy (11s)
Publishing service to the Serverless Dashboard...
Successfully published your service to the Serverless Dashboard: https://app.serverless.com/adamgoldman/apps/lambdas/lambdas/dev/ap-northeast-1
Environment: linux, node 18.7.0, framework 3.26.0 (local), plugin 6.2.2, SDK 4.3.2
Credentials: Serverless Dashboard, "default" provider (https://app.serverless.com/adamgoldman/apps/lambdas/lambdas/dev/ap-northeast-1/providers)
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues
Error:
ChangeSet lambdas-dev-change-set cannot be created due to a mismatch with existing attribute Template

Service configuration (serverless.yml) content

functions:
  prompt-next-process:
    handler: handler.promptNextProcess
  prompt-scheduled-process:
    handler: handler.promptScheduledProcess

org: adamgoldman
app: lambdas
service: lambdas
frameworkVersion: "3"
useDotenv: true

provider:
  name: aws
  region: ap-northeast-1
  runtime: nodejs16.x
  environment:
    RESPOND_API_TOKEN: ${param:RESPOND_API_TOKEN}
    MONGODB_URI: ${param:MONGODB_URI}
    NODE_ENV: ${param:NODE_ENV}

plugins:
  - serverless-esbuild
  - serverless-offline

package:
  individually: true
  excludeDevDependencies: true




### Command name and used flags

NODE_ENV=development sls deploy --verbose --stage=dev

### Command output

```shell
See "issue description"

Environment information

$ serverless --version
Running "serverless" from node_modules
Framework Core: 3.26.0 (local) 3.26.0 (global)
Plugin: 6.2.2
SDK: 4.3.2

Guia do colaborador

Pilha de tecnologia
javascriptnodejsaws
Domain
clouddevops
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
4
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
3-5 days
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Understanding of AWS CloudFormationExperience with Serverless FrameworkNode.js debugging skills
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
20
Direção de pesquisa
Investigate the intermittent 'ChangeSet cannot be created due to a mismatch with existing attribute Template' error during deployment. Focus on the serverless framework's deploy logic that creates CloudFormation change sets, specifically in the AWS provider class (likely in `lib/plugins/aws/deploy/lib/createChangeSet.js`). The error suggests a mismatch between the current template and the one CloudFormation expects, possibly due to race conditions or stale state. Check the issue comments for any additional context, and consider testing with the ` verbose` flag to capture more details. Look into whether the issue is related to the `serverless esbuild` plugin's handling of compiled code or AWS API rate limits.