-
-
Notifications
You must be signed in to change notification settings - Fork 451
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
Subsequent puppet runs fail on unauthenticated replicasets #731
Comments
I observe the same failure using MongoDB 4.4.27. |
Running on 3 nodes sequentially results in 3 different replicasets, each with the same name and a single member. Instead of doing a single run on every node, expanding the set with every run, I now tried setting up the nodes first , then creating the set with all 3 nodes at once. This results in only the one where the set is initiated as the single member of the set. Detection of the current set is clearly not working as intended:
Since no set actually exists, this results in the provider accidentally doing the right thing and initiates the set. However the current detection of dead and alive members is also wrong.
This in turn again creates a set with a single member. |
This seems to be caused by custom configuration:
The resulting config file:
Problem was entirely on my side. |
Module version: current master
MongoDB version: 6.0.12
The current provider implementation fails on subsequent runs with the message:
The
self.instances
method fails to correctly fill up the current resources:The text was updated successfully, but these errors were encountered: