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.

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

Stack deployment failed #233

Closed
AGronowski opened this issue Oct 17, 2023 · 2 comments · Fixed by #234
Closed

Stack deployment failed #233

AGronowski opened this issue Oct 17, 2023 · 2 comments · Fixed by #234
Labels
bug Something isn't working

Comments

@AGronowski
Copy link

Describe the bug

I tried reinstalling the stack and now it doesnt work.

Expected Behavior

Stack deploys successfully

Current Behavior

2023-10-17 16:16:06 UTC+0100 | LambdaStartDeployRolePolicy055A2336 | CREATE_FAILED | Resource handler returned message: "The role with name LambdaStartDeployRole cannot be found. (Service: Iam, Status Code: 404, Request ID: 3fa4dbbf-86f3-4139-9b33-a02d27d186e1)" (RequestToken: 102dbe91-3b34-f666-9019-99ee9c8cbbc6, HandlerErrorCode: NotFound)

The failure is in the nested stack SdAsyncInferStNestedStackSdAsyncInferStNestedStackResourc-1H1BTOYSBFUO7.

Previously I was getting a failure because of: Resource handler returned message: "Resource of type 'AWS::IAM::Role' with identifier 'LambdaStartDeployRole' already exists." (RequestToken: fb433b47-d4b7-2308-136f-4de408bff86f, HandlerErrorCode: AlreadyExists)

So now I deleted LambdaStartDeployRole, but that results in the "The role with name LambdaStartDeployRole cannot be found." No matter whether I delete or keep LambdaStartDeployRole, things don't deploy.

Reproduction Steps

deploy the stack

Possible Solution

No response

Additional Information/Context

No response

Solution Version

v1.2.0-d328a45

AWS Region. e.g., us-east-1

us-east-1

Other information

No response

@AGronowski AGronowski added the bug Something isn't working label Oct 17, 2023
@alvindaiyan alvindaiyan linked a pull request Oct 18, 2023 that will close this issue
4 tasks
@alvindaiyan
Copy link
Contributor

Hi, the issue is now under investigation. For now, if you first deploy failed, try deploy again with useExist = yes and existS3Bucket to your previous s3 bucket name

@AGronowski
Copy link
Author

Thanks. I followed your advice and now the stack deployed successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants