-
Notifications
You must be signed in to change notification settings - Fork 7
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
[BUG] Build files contain CFN tokens until stack is updated #184
Comments
cartalla
added a commit
that referenced
this issue
Dec 29, 2023
Otherwise they contain CloudFormation tokens for resources used during deployment. Limit Rocky 8 to 8.8 since 8.9 fails because lustre client isn't suported. Resolves #184
cartalla
added a commit
that referenced
this issue
Jan 4, 2024
Otherwise they contain CloudFormation tokens for resources used during deployment. Limit Rocky 8 to 8.8 since 8.9 fails because lustre client isn't suported. Check AMI support for instance types. Rocky 8 doesn't currently support the gen7 AMD instance types. Resolves #184 Resolves #185 Resolves #186
cartalla
added a commit
that referenced
this issue
Jan 5, 2024
Otherwise they contain CloudFormation tokens for resources used during deployment. Limit Rocky 8 to 8.8 since 8.9 fails because lustre client isn't suported. Check AMI support for instance types. Rocky 8 doesn't currently support the gen7 AMD instance types. Publish to ErrorSnsTopicArn when a lambda fails. Resolves #184 Resolves #185 Resolves #186
cartalla
added a commit
that referenced
this issue
Jan 5, 2024
Otherwise they contain CloudFormation tokens for resources used during deployment. Limit Rocky 8 to 8.8 since 8.9 fails because lustre client isn't suported. Check AMI support for instance types. Rocky 8 doesn't currently support the gen7 AMD instance types. Publish to ErrorSnsTopicArn when a lambda fails. Resolves #184 Resolves #185 Resolves #186
cartalla
added a commit
that referenced
this issue
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The build files are currently built with the cdk stack so resources like security groups and IAM policies don't exist yet.
There is code to get those IDs on an update, but the files should really be correct after initial deployment.
Propose to create them in a Lambda custom resource with the resource IDs passed as parameters so that they are resolved
during CFN deployment.
The ParallelCluster custom resource should depend on the build-files since it will download the build files from S3.
The text was updated successfully, but these errors were encountered: