[SERVER-8221] Using copyDatabase to copy from an unauthenticated instance to an authenticated instance fails Created: 17/Jan/13 Updated: 10/Dec/14 Resolved: 22/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Security |
| Affects Version/s: | 2.2.1, 2.2.3, 2.4.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mark T | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB shell version: 2.2.1 |
||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: | 1. Log into an authenticated server Results in: Thu Jan 17 15:40:59 DBClientCursor::init call() failed to: 127.0.0.1:27017 |
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Comments |
| Comment by Spencer Brody (Inactive) [ 21/Feb/13 ] | |||||||
|
On the 2.4.0 release candidate this fails without an error message:
and there is a message in the target DB's log saying:
| |||||||
| Comment by Spencer Brody (Inactive) [ 21/Feb/13 ] | |||||||
|
in 2.2.3, rather than crashing the target (authenticated) instance, you get back:
| |||||||
| Comment by Spencer Brody (Inactive) [ 21/Feb/13 ] | |||||||
|
Reproduced the problem with 2.2.1. The source database doesn't have to be sharded - the important thing is copying from an unauthed instance to an authenticated instance. |