[SERVER-12885] 2.6 mongodump writes no output files when dumping "system.users" Created: 25/Feb/14  Updated: 11/Jul/16  Resolved: 28/Feb/14

Status: Closed
Project: Core Server
Component/s: Security, Tools
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Michael O'Brien Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

With mongodump-2.4, this works:

$ mongodump-2.4 -d "admin" -c "system.users"
connected to: 127.0.0.1
Tue Feb 25 13:53:12.167 DATABASE: admin	 to 	dump/admin
Tue Feb 25 13:53:12.167 	admin.system.users to dump/admin/system.users.bson
Tue Feb 25 13:53:12.168 		 1 objects
Tue Feb 25 13:53:12.168 	Metadata for admin.system.users to dump/admin/system.users.metadata.json
$

but doing the same thing, against the same db, with 2.6rc0 mongodump writes no output file:

$ mongodump-2.6 -d "admin" -c "system.users"
connected to: 127.0.0.1
2014-02-25T13:54:36.635-0500 DATABASE: admin	 to 	dump/admin
$

however, it looks like other collections (system.roles, system.version, etc) do get dumped as expected.

We need to be able to dump system.users in order to complete the multi-tenant user dump/restore process outlined in Matt's comment on QA-404:

https://jira.mongodb.org/browse/QA-404?focusedCommentId=479218&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-479218



 Comments   
Comment by Githook User [ 28/Feb/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-12885 Make sure mongodump can dump admin.system.users when explicitly asked to
Branch: master
https://github.com/mongodb/mongo/commit/59de90f6d4b1aa9e753921031f1f821611720a2f

Comment by Spencer Brody (Inactive) [ 26/Feb/14 ]

Reproduced

Generated at Thu Feb 08 03:29:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.