pulumi: Intermittent "NoSuchKey: The specified key does not exist" errors when using S3 backend

I have been following the cloud backend change

https://github.com/pulumi/pulumi/pull/2455

When trying to run pulumi login s3://pulumi-state-files and then pulumi up

I get the following error error: failed to load checkpoint: blob (code=NotFound): NoSuchKey: The specified key does not exist. I can navigate and interrogate that specific S3 bucket via the AWS CLI and have setup the appropriate AWS_PROFILE environment.

Not quite sure what I am doing incorrectly, I have followed all the documentation and issue steps I have been able to find.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 3
Comments: 28 (22 by maintainers)

Commits related to this issue

Do not attempt to load checkpoint before saving a snapshot For historical reasons, we used to need to require to load an existing checkpoint to copy some data from it into the snapshot when saving a ... — committed to pulumi/pulumi by ellismg 5 years ago
Do not attempt to load checkpoint before saving a snapshot For historical reasons, we used to need to require to load an existing checkpoint to copy some data from it into the snapshot when saving a ... — committed to pulumi/pulumi by ellismg 5 years ago
Do not attempt to load checkpoint before saving a snapshot For historical reasons, we used to need to require to load an existing checkpoint to copy some data from it into the snapshot when saving a ... — committed to pulumi/pulumi by ellismg 5 years ago

Most upvoted comments

I should note that a single bucket can handle all of the stage cross-accounts.

export AWS_PROFILE=... 
export AWS_REGION=.. 
pulumi login s3://bucket

other pulumi up etc operations will follow this - but if you set stack config aws:profile: newprofile the stack itself will follow the stack’s profile, not the env var (at least in my light testing). state will still store based on the env var and login.

keen99 on Jun 6, 2019

I’m ok keeping this issue open. It’s a good documentation of the problem. If we opened a new issue, we’d just have to link back to this for whoever works on it to understand what’s going on and get teh necessary context.

Thanks!

CyrusNajmabadi on May 31, 2019