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

add default value for master-node when provisioning cluster using OSB #621

Merged
merged 1 commit into from
Aug 20, 2024

Conversation

OVI3D0
Copy link
Member

@OVI3D0 OVI3D0 commented Aug 19, 2024

Description

As mentioned by @gkamat, when provisioning a cluster in OSB, the master node specification should match the node name. This change ensures that these two values always match, by performing a check before building the cluster and ensuring the two values match before moving on.

Issues Resolved

#380

Testing

  • [✔️] New functionality includes testing

tested with make test + make it and by provisioning clusters with mismatched values, as well as missing values for either node-name or master-node value.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Collaborator

@IanHoang IanHoang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@IanHoang IanHoang merged commit f4ab3ab into opensearch-project:main Aug 20, 2024
10 checks passed
gkamat pushed a commit to gkamat/opensearch-benchmark that referenced this pull request Aug 22, 2024
f"The provided --node-name '{node_name}' and --master-nodes '{master_nodes}' are different. "
f"Using '{node_name}' for both node name and initial master node."
)
master_nodes = [node_name]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering, If this is the desired behavior then do we want to expose master_nodes ? Here we are reporting error but override the master_nodes values and continue with provisioning. I think we should either fail so that user is notified or not expose the master_nodes field at all. @IanHoang would like to know your thoughts as well

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 this pull request may close these issues.

3 participants