-
Notifications
You must be signed in to change notification settings - Fork 3
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
Replicaset configuration #124
Comments
not at this moment. you issue is probably related to stuff in #118 |
one option I found to avoid the search() issue with chef-solo is to do:
and do the rs config on the nodes manually |
yeah, we really need to support manually setting the replicaset members via node attribute and parameter to |
Seems like I'll actually get the fancy stuff first, see #215 @jamesonjlee this seems safe to close |
I'm having some issues configuring a replicaset and had a few questions.
The general problem is this:
xxx.xxxxx.biz [2013-06-03T19:13:58+00:00] WARN: Cannot configure replicaset 'rep1', no member nodes found
I get this on every node I try to start. Related to the search for other nodes, which don't exist yet? I seem to have the same problem even when I have other nodes up. Is there any way to override the search and just set members via attribute?
EDIT: This is using Chef Server 11 and Chef 11.4.4
The text was updated successfully, but these errors were encountered: