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

[patch] sls_mongodb_cfg_file for custom mongodb namespace #1456

Merged
merged 12 commits into from
Feb 7, 2025

Conversation

sarthakSharma5
Copy link
Contributor

@sarthakSharma5 sarthakSharma5 commented Feb 5, 2025

Fix for sls_mongodb_cfg_file path

Fixes a bug which causes install failure in SLS stage when using non-interactive method and a custom MongoDB namespace is provided in parameters.

Sets the parameter sls_mongodb_cfg_file to /workspace/configs/mongo-{mongodb_namespace}.yml

Issue

By default, MAS installation fails when using the non-interactive method and opting for a custom MongoDB namespace.
This happens because the value for the parameter sls_mongodb_cfg_file remains at default, which is then used by the mas_devops.sls role and causes a failure since the config file is not present at the path provided (which defaults to /workspace/configs/mongo-mongoce.yml).

To Replicate use --mongodb-namespace "mongoce-$MAS_INSTANCE_ID" with the non-interactive install command.

Before Fix (failing SLS task during install)

image

After Fix (with successful FVT run)

- SLS task run
image
- FVT Runs for a MAS Installation (with IoT)
image

@sarthakSharma5 sarthakSharma5 changed the title [patch] sls_mongodb_cfg_file value for custom MongoDB Namespace [patch] sls_mongodb_cfg_file for custom mongodb namespace Feb 5, 2025
@sarthakSharma5 sarthakSharma5 marked this pull request as ready for review February 5, 2025 16:17
@durera durera merged commit 130727d into master Feb 7, 2025
12 checks passed
@durera durera deleted the slsmongocfg.ns branch February 7, 2025 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants