[DOCS-5919] Add needed role for clusterManager before converting standalone to replica set Created: 28/Jul/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Minor - P4
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: conversion, replica-set
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/tutorial/convert-standalone-to-replica-set/
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0
Screen Resolution: 1920 x 1080
repo: docs
source: tutorial/convert-standalone-to-replica-set


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.2

 Description   

This manual page does not mention what happens if you have already created users in the standalone database, before converting it to a replica set. I have sought for a solution for a long time, because I was not able to issue 'rs.initiate()', with the error "not authorized to execute command on admin".

I think it is valuable to explain that, if you have existing users, one of them should be granted the 'clusterManager' role: http://docs.mongodb.org/v2.6/reference/built-in-roles/
Then, this user can be used to log in to the Mongo shell and issue 'rs.initiate()'



 Comments   
Comment by Education Bot [ 01/Nov/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!

Generated at Thu Feb 08 07:51:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.