[SERVER-51177] RenameCollection with non-existing target DB fails with misleading message Created: 28/Sep/20 Updated: 27/Oct/23 Resolved: 28/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
When issuing the renameCollection command with a non-existing target DB, the returned error message is "target namespace exists". Easy way to reproduce the error: prepend whatever string to the target nss in this line of the jstests/sharding/read_write_concern_defaults_application.js test:
|
| Comments |
| Comment by Pierlauro Sciarelli [ 28/Sep/20 ] |
|
False alarm, closing because works as expected: in that specific test the db is reused hence needs to be dropped before new iterations. So the error message is legit. |