Channels
#aws
Title
# aws
m
most-state-94104
05/16/2022, 1:15 PMI have created an S3 bucket to use with a MWAA environment. When I run pulumi up, pulumi wants to delete and recreate the bucket:
Copy code
+ aws:s3:Bucket aaa creating
+ aws:s3:Bucket aaa creating error: 1 error occurred:
+ aws:s3:Bucket aaa **creating failed** error: 1 error occurred:
Diagnostics:
aws:s3:Bucket (aaa):
error: 1 error occurred:
* Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
status code: 409, request id: Q3A6YB3N22Y5T7WW, host id: huiDWKeYcWdOUbIIjq/h4RlUSNCXA1yQG0l85af5uXLaZpVFsnHXVD5lUkP0QRmGTiPFLajBiwo=v
victorious-church-57397
05/16/2022, 1:21 PMdid you create the bucket with pulumi?
m
most-state-94104
05/16/2022, 1:22 PMYes
v
victorious-church-57397
05/16/2022, 1:22 PMhmm, maybe try running a
pulumi refreshm
most-state-94104
05/16/2022, 1:22 PMI tried that already
v
victorious-church-57397
05/16/2022, 1:23 PMcan you send the full log trace? where it says its deleting and recreating it? i’ve never experienced anything like this with pulumi before tbh
if its just trying to create, and not delete it, then its indicative that the bucket was created with another pulumi stack or by other means, and its trying to recreate the bucket. if thats the case then i’d recommend importing the resource in to pulumi
m
most-state-94104
05/16/2022, 1:27 PMIt is trying to delete it as well - I’ll send the preview log trace one sec
Copy code
~ aws:s3:Bucket aaa refreshing
@ previewing update.....
+ aws:s3:Bucket aaa create
- aws:s3:Bucket aaa deleteNote that I haven’t included the full log because the stack is quite large
v
victorious-church-57397
05/16/2022, 1:31 PMso its trying to create it before it deletes it? thats a bit strange. have you tried removing the resource definition altogether and putting it back in
m
most-state-94104
05/16/2022, 1:33 PMResource definition ?
Sorry I’m not familiar with that
b
billowy-army-68599
05/16/2022, 1:33 PM
@most-state-94104 can you show the diff from pulumi preview ?
👀 1
This usually happens because the resource name is changing on each run, also sharing the code you're using to define the bucket helps
m
most-state-94104
05/16/2022, 1:35 PMThe name is the same (it doesn’t include a sha)
Unfortunately the repo is internal, so I’ll have to post the details here. Give me a minute
b
billowy-army-68599
05/16/2022, 1:38 PM
The diff output will help as well
m
most-state-94104
05/16/2022, 2:10 PMSorry the bucket is created through another internal repo and is quite complex (it includes various optional settings) so not the easiest to share. Will post this afternoon (along with the diff) 🙂
v
victorious-church-57397
05/16/2022, 2:10 PMif the bucket is created by another repo, then thats why you’re getting the error
you’re trying to create a bucket with the same name twice
S3 buckets’ names are globally defined, therefor each bucket name has to be unique, if you’re trying to reference the same bucket from another stack, I’d recommend using pulumi stack references to achieve this: https://www.pulumi.com/learn/building-with-pulumi/stack-references/
m
most-state-94104
05/16/2022, 2:14 PMSorry what I meant is that the function for creating the bucket is defined in another repo and packaged as a library
v
victorious-church-57397
05/16/2022, 2:15 PMah right ok
m
most-state-94104
05/16/2022, 2:15 PMWe create the bucket by calling the function in the repo where the rest of the stack is created
v
victorious-church-57397
05/16/2022, 2:15 PMif you could send some snippets over that would be really helpful
m
most-state-94104
05/16/2022, 2:16 PMI’m going to ask my manager why the repo is internal - I can’t see anything sensitive
Reached out to my colleague and turns out the problem is because I reset the PULUMI_CONFIG_PASSPHRASE. This meant pulumi was trying to recreate the stack, so the solution is to revert the stack from a backup
👍 2
5 Views