serverless: Failed deployment - ChangeSet does not exist
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 version?
- Yes, I’m using the latest version
Is there an existing issue for this?
- I have searched existing issues, it hasn’t been reported yet
Issue description
Serverless deployment is failing occasionally, saying that ChangeSet does not exist. If I rerun it will work.
Service configuration (serverless.yml) content
service: service-name
projectDir: ../../
plugins:
- serverless-s3-sync
custom:
bucketName: name-${env:STAGE}
s3Sync:
- bucketName: ${self:custom.bucketName}
bucketPrefix: ${env:PR_NUMBER}
localDir: dist
provider:
name: aws
runtime: nodejs12.x
stage: ${env:STAGE}
resources:
Resources:
StaticSite:
Type: AWS::S3::Bucket
Properties:
BucketName: ${self:custom.bucketName}
CorsConfiguration:
CorsRules:
- AllowedHeaders:
- '*'
AllowedMethods:
- GET
AllowedOrigins:
- 'https://*.${env:DOMAIN}'
StaticSiteS3BucketPolicy:
Type: AWS::S3::BucketPolicy
Properties:
Bucket:
Ref: StaticSite
PolicyDocument:
Statement:
- Effect: Allow
Action:
- s3:GetObject
Resource: !Sub '${StaticSite.Arn}/*'
Principal:
CanonicalUser: ${cf:apps-${env:STAGE}.S3CanonicalUserId}
Command name and used flags
sls deploy --verbose
Command output
Waiting for new change set to be created
× Stack apps-navigation-shell-dev failed to deploy (2s)
Environment: linux, node 16.13.2, framework 3.2.1 (local), plugin 6.0.0, SDK 4.3.1
Credentials: Local, environment variables
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
ChangeSet [apps-navigation-shell-dev-change-set] does not exist
1 deprecation found: run 'serverless doctor' for more details
Waiting for new change set to be created
Environment information
Framework Core: 3.2.1 (local)
Plugin: 6.0.0
SDK: 4.3.1
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (8 by maintainers)
Thank you so much for your help, will close this issue now! 😄
Hey 👋 Honestly, at the moment there are virtually no benefits - the only one is having a bit nicer progress bar during update, thanks to having a changeset, we exactly know what will be updated during an update so we can show the numbers (e.g. 3/15) in the progress bar.
We have future plans to introduce features where you can create a changeset without deploying it, which allows you to inspect the changes that will be applied before actually applying them. It might be useful in migrations, addressing breaking changes, etc. But it’s not available yet and we don’t have an ETA for that.
Thanks a lot @adrianaferrugento 🙇 I’ll be looking into that, the report will be very helpful 🙇