We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi. I'am trying to contribute this role. Faced this error many times. This one after updating mongo from 4.0 to 4.2
TASK [undergreen.mongodb.4.2 : Replication configuration | 2nd Pt] ********************************************************* skipping: [development-mongodb-2] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-1.xxx.io'}) skipping: [development-mongodb-2] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-2.xxx.io'}) skipping: [development-mongodb-2] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-3.xxx.io'}) skipping: [development-mongodb-3] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-1.xxx.io'}) skipping: [development-mongodb-3] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-2.xxx.io'}) skipping: [development-mongodb-3] => (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-3.xxx.io'}) failed: [development-mongodb-1] (item={u'host_port': 27017, u'host_type': u'replica', u'host_name': u'development-mongodb-1.xxx.io'}) => {"ansible_loop_var": "item", "changed": false, "item": {"host_name": "development-mongodb-1.xxx.io", "host_port": 27017, "host_type": "replica"}, "msg": "Unable to initiate replica set: already initialized"}
The text was updated successfully, but these errors were encountered:
There should be a workaround to separate nodes in replica set to standalone instances. I think that should help with workaround in such cases.
Sorry, something went wrong.
No branches or pull requests
Hi. I'am trying to contribute this role. Faced this error many times. This one after updating mongo from 4.0 to 4.2
The text was updated successfully, but these errors were encountered: