Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Race condition when using self managed deployment type #438

Open
tabrezm opened this issue May 5, 2024 · 0 comments · May be fixed by #439
Open

Race condition when using self managed deployment type #438

tabrezm opened this issue May 5, 2024 · 0 comments · May be fixed by #439

Comments

@tabrezm
Copy link

tabrezm commented May 5, 2024

I'm hitting a race condition when using a self managed deployment. It looks like the stack set resource starts deploying before the IAM role is ready, resulting in the following error message:

Resource handler returned message: "Resource of type 'Stack set operation [133a0012-7a7e-4ca6-a253-622c36c8d8d8] was unexpectedly stopped or failed. status reason(s): [Account <REDACTED> should have 'AWSCloudFormationStackSetExecutionRole' role with trust relationship to Role '<REDACTED>-AdminRole38563C57-xWR5IEOHv72o'.]' with identifier '<REDACTED>StackSet0EB2B840:bebe8bba-591e-4dd4-a637-1d631421d4d8' did not stabilize."

If I pre-create the admin role and specify it in the StackSet resource, it deploys successfully. Note that it does expose another minor issue, where a duplicate policy is always added to the role.
@tabrezm tabrezm linked a pull request May 5, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: create assume role policy inline tabrezm/cdk-stacksets
1 participant
@tabrezm