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

[BUG] Handle case where ParallelCluster database stack isn't ready yet #190

Closed
cartalla opened this issue Jan 11, 2024 · 0 comments · Fixed by #192
Closed

[BUG] Handle case where ParallelCluster database stack isn't ready yet #190

cartalla opened this issue Jan 11, 2024 · 0 comments · Fixed by #192
Assignees

Comments

@cartalla
Copy link
Contributor

cartalla commented Jan 11, 2024

Describe the bug
I specified slurm/PartallelClusterConfig/Database/DatabaseStackName and tried to deploy the cluster before the database
stack had finished deploying.
This failed with stack trace because the stack wasn't found or the stack didn't have outputs yet.

Add checking for an incorrect stack or stack that isn't ready so get better error messages.

@cartalla cartalla self-assigned this Jan 11, 2024
cartalla added a commit that referenced this issue Jan 19, 2024
Handle case where ParallelClusterConfig DatabaseStackName isn't ready yet.

Resolves #190

Don't create self.configure_cluster_manager_sns_topic_arn_parameter if
RESEnvironmentName not configured.

Resolves #189
cartalla added a commit that referenced this issue Jan 19, 2024
Don't create self.configure_cluster_manager_sns_topic_arn_parameter if
RESEnvironmentName not configured.

Rename variables and lambdas for RES related configuration to include "Res" for clarity.

Resolves #189

Handle case where ParallelClusterConfig DatabaseStackName isn't ready yet.

Resolves #190
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant