[cli] bootstrap upgrade to version 4 fails after upgrade from 1.60.0 to 1.61.0
See original GitHub issueBootstrapped using new style CDK bootstrap (BootstrapVersion: 3), then upgraded to CDK 1.61. Got errors like:
❌ InitiativeConfigStack-development failed: Error: InitiativeConfigStack-development: publishing assets requires bootstrap stack version '4', found '3'. Please run 'cdk bootstrap' with a newer CLI version.
Did as instructed in the error and #8678 , but got the following:
env CDK_NEW_BOOTSTRAP=1 npx cdk bootstrap --cloudformation-execution-policies arn:aws:iam::aws:policy/AdministratorAccess aws://123456789012/eu-west-1
(node:69834) ExperimentalWarning: The fs.promises API is experimental
CDK_NEW_BOOTSTRAP set, using new-style bootstrapping
⏳ Bootstrapping environment aws://123456789012/eu-west-1...
❌ Environment aws://123456789012/eu-west-1 failed bootstrapping: Error: Not downgrading existing bootstrap stack from version '3' to version '0'. Use --force to force.
Not downgrading existing bootstrap stack from version '3' to version '0'. Use --force to force.
Am I missing something obvious here?
- CLI Version : 1.61.0
- Framework Version: 1.61.0
- Node.js Version: v10.16.3
- OS : mac
- Language (Version):
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Migrating to v4 - Bootstrap
Moving from Beta 3 to our stable v4.x release, there are no breaking changes, but there are some notable ... Updated selector for...
Read more >November 2022 (version 1.74) - Visual Studio Code
Learn what is new in the Visual Studio Code November 2022 Release (1.74)
Read more >BOOTSTRAP_HOST_UUID_CO...
Variable, BOOTSTRAP_HOST_UUID_COOKIE ; Description, Sets a unique identifier of the local filesystem contents ; Default, none ...
Read more >Bug List - FreeBSD Bugzilla
This list is too long for Bugzilla's little mind; the Next/Prev/First/Last buttons ... www/adguardhome: fails to start after go1.18.9 update, Mon 09:57.
Read more >Amazon ECS Linux container agent versions
Amazon ECS‑optimized Amazon Linux AMI Amazon ECS container agent version Docker v...
2018.03.20221115 1.51.0 20.10.13
2018.03.20221010 1.51.0 20.10.13
2018.03.20220627 1.51.0 20.10.13
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
Hi @suyashdb yes I have resolved this issue. There are few scenarios. First of all I was using old version of CDK which uses old bootstrap version and when I upgraded my CDK app to new version i.e. 1.64.1 which uses new version of bootstrap i.e. bootstrap V4 I started getting above mentioned error.
So I had to bootstrap my target AWS account again with new bootstrap version so that it will create required bootstrap parameter in SSM param store So you should have this parameter in your param store - “/cdk-bootstrap/${Qualifier}/version” where ${Qualifier} is hnb659fds but looking at your error I think you are not using default qualifier, you are using qualifier - fcc-tsi So you should have this parameter in you param store /cdk-bootstrap/fcc-tsi/version
Another thing is your parameter type should be string and not SecureString because aws cloud formation template does not support SecureString yet. Our cloud security team converted all the parameters in our param store to SecureString and that took some time for me to realize.
patch to fix bootstrapping issue was released in 1.61.1