[DOCS-9176] rs.initiate() comes too late in 2.6 procedure for Deploy Replica Set and Configure Authentication and Authorization Created: 19/Oct/16 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shannon Bradshaw (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
https://github.com/mongodb/docs/blob/v2.6/source/tutorial/deploy-replica-set-with-auth.txt Per sharad.aggarwal: if I start the node as replica set, I cannot add user w/o doing an rs.initiate() which in these instructions is step 8. If I start the node as standalone, then the user I created in step 2 will not be replicated to other nodes What I ended up doing was do rs.initiate() and then create user |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Sharad Aggarwal [ 20/Oct/16 ] |
|
stennie, as discussed with mark.helmstetter, I think we need to state that in step 1, the node should be started as standalone. The customer started the node a rs and createUser failed because replicaset had not been initiated. |