[DOCS-12592] Restoring from Sharded Collection instructions fail with authentication Created: 02/Apr/19  Updated: 30/Oct/23  Resolved: 02/May/19

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

Type: Task Priority: Major - P3
Reporter: Danny Hatcher (Inactive) Assignee: Ravind Kumar (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-40434 Root user can't delete minOpTimeRecov... Closed
Participants:
Days since reply: 4 years, 40 weeks, 6 days ago
Story Points: 1

 Description   

Description

The instructions for restoring a sharding cluster from an existing backup will error at step D-3 (removing minOpTimeRecovery document) if authentication is enabled for the process as normal users do not have the appropriate rights to delete from the admin.system.versions. The instructions should account for authentication.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 02/May/19 ]

Author:

{'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}

Message: DOCS-12592: Fix steps in restore sharded cluster tutorial
Branch: v3.4
https://github.com/mongodb/docs/commit/636f003497db14bf4c6f85ee769e8b116c15efd3

Comment by Githook User [ 02/May/19 ]

Author:

{'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}

Message: DOCS-12592: Authentication for sharded restoration
Branch: v3.4
https://github.com/mongodb/docs/commit/f3ea5577f7353624190a6a2a91f7776d36c0ad8c

Comment by Githook User [ 02/May/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12592: Authentication for sharded restoration
Branch: v3.6
https://github.com/mongodb/docs/commit/25cf2280e667aefa6faf9effc2b2d81fcea03dd5

Comment by Githook User [ 02/May/19 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}

Message: DOCS-12592: Authentication for sharded restoration
Branch: v4.0
https://github.com/mongodb/docs/commit/0ffafcb722f6bbb2e1688ce8b9f77ee91b72a6ab

Comment by Githook User [ 02/May/19 ]

Author:

{'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}

Message: DOCS-12592: Authentication for sharded restoration
Branch: master
https://github.com/mongodb/docs/commit/7c3d4c22fbfdeb3498cffbb2d457946935959d2a

Comment by Ravind Kumar (Inactive) [ 02/May/19 ]

Currently doing a final test build before merging this to master. Will backport through to 3.4.

Comment by Spencer Jackson [ 02/Apr/19 ]

root doesn't have every privilege, it just has a large number of safe privileges for user collections. System collections that are not intended to be messed with tend to remain locked down. We've sometimes granted privileges to the restore role to make restoration easier, but generally only under duress.

Is this a problem for 4.0/4.2, or just 3.6 which is the linked document? Will every sharded restore need to perform this operation?

Generated at Thu Feb 08 08:05:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.