v1.109.0 CLI cuts off step progress and outputs misleading "Failed resources:" message
See original GitHub issueWhen deploying an AWS stack using v1.109.0 the CLI…
- Outputs “Failed resources:” message even if all resources were deployed successfully.
- Does not print finished progress of every step.
Reproduction Steps
Upgrade from 1.108.1 to 1.109.0.
What did you expect to happen?
AWS stacks should deploy as they did before.
CDK_NEW_BOOTSTRAP set, using new-style bootstrapping
⏳ Bootstrapping environment aws://##########/eu-west-1...
Trusted accounts for deployment: (none)
Trusted accounts for lookup: (none)
Using default execution policy of 'arn:aws:iam::aws:policy/AdministratorAccess'. Pass '--cloudformation-execution-policies' to customize.
AN_AWS_STACK: creating CloudFormation changeset...
0/4 | 15:13:48 | UPDATE_IN_PROGRESS | AWS::CloudFormation::Stack | AN_AWS_STACK User Initiated
0/4 | 15:13:54 | UPDATE_IN_PROGRESS | AWS::IAM::Role | FilePublishingRole
0/4 | 15:13:54 | UPDATE_IN_PROGRESS | AWS::IAM::Role | ImagePublishingRole
0/4 | 15:13:55 | UPDATE_IN_PROGRESS | AWS::IAM::Role | DeploymentActionRole
3/4 | 15:14:10 | UPDATE_COMPLETE | AWS::IAM::Role | ImagePublishingRole
3/4 | 15:14:10 | UPDATE_COMPLETE | AWS::IAM::Role | FilePublishingRole
3/4 | 15:14:10 | UPDATE_COMPLETE | AWS::IAM::Role | DeploymentActionRole
4/4 | 15:14:15 | UPDATE_COMPLETE_CLEA | AWS::CloudFormation::Stack | AN_AWS_STACK
4/4 | 15:14:15 | UPDATE_COMPLETE | AWS::CloudFormation::Stack | AN_AWS_STACK
✅ Environment aws://##########/eu-west-1 bootstrapped.
What actually happened?
The stack deployment fails to clean up, although the stack itself does get deployed.
CDK_NEW_BOOTSTRAP set, using new-style bootstrapping
⏳ Bootstrapping environment aws://##########/eu-west-1...
Trusted accounts for deployment: (none)
Trusted accounts for lookup: (none)
Using default execution policy of 'arn:aws:iam::aws:policy/AdministratorAccess'. Pass '--cloudformation-execution-policies' to customize.
AN_AWS_STACK: creating CloudFormation changeset...
0/4 |15:20:04 | UPDATE_IN_PROGRESS | AWS::CloudFormation::Stack | AN_AWS_STACK User Initiated
0/4 |15:20:11 | UPDATE_IN_PROGRESS | AWS::IAM::Role | DeploymentActionRole
0/4 |15:20:11 | UPDATE_IN_PROGRESS | AWS::IAM::Role | FilePublishingRole
0/4 |15:20:11 | UPDATE_IN_PROGRESS | AWS::IAM::Role | ImagePublishingRole
3/4 |15:20:28 | UPDATE_COMPLETE | AWS::IAM::Role | FilePublishingRole
3/4 |15:20:28 | UPDATE_COMPLETE | AWS::IAM::Role | ImagePublishingRole
3/4 |15:20:28 | UPDATE_COMPLETE | AWS::IAM::Role | DeploymentActionRole
Failed resources:
✅ Environment aws://##########/eu-west-1 bootstrapped.
Notice that step 4/4 did not print.
Environment
- **CDK CLI Version :1.109.0
- **Framework Version:1.109.0
- Node.js Version: 14.17.0
- **OS :Windows 10
- Language (Version): 4.3.2
Other
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Release Notes | Google Cloud CLI Documentation
Fixed crash in gcloud beta functions deploy --gen2 failures causing the error message "This stage does not belong to this progress tracker".
Read more >New Features Guide - FortiOS 7.0.0 - Amazon AWS
An error message appears, Invalid IPv6 address, and lists the reasons for the error. In this example, the interface MTU setting must be...
Read more >ASR 5500 System Administration Guide, StarOS Release 21.10
The output of the error message is shown below: CLI print failure Failure: SSH V1 contains multiple structural vulnerabilities and is no.
Read more >EXO User Manual - YSI
Twist the battery cover clockwise until it stops at the rubber gasket. ... If a battery failure occurs that results in battery acid...
Read more >QL-300 User Guide
Wait a moment, and the machine's power automatically turns off and the LED ... printer for the adjustment results and whether to apply...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I missed that bug, sorry about that. I opened a PR to fix the misleading
Failed resources:
message but will need to dedicate more time into investigating the cutoff of step progress output.I am marking this issue as p1 due to the number of users that will be impacted. It has been prioritized as important and should see attention soon. We use +1s to help us prioritize our work.
⚠️COMMENT VISIBILITY WARNING⚠️
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.