[SERVER-11258] jstests\sharding\addShard1.js fails when given a db prefix Created: 17/Oct/13  Updated: 28/Oct/13  Resolved: 23/Oct/13

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 2.5.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sridhar Nanjundeswaran Assignee: Kyle Erf
Resolution: Duplicate Votes: 0
Labels: 26qa, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 Enterprise Build on 2008 R2
Git hash:
mongo - 1ea7e56cb2b8653d4b0453f04728033df34be9e1
enterprise - d919ef07f817832732d2a0a2ec68251bc161193a


Issue Links:
Depends
Operating System: ALL
Steps To Reproduce:

python buildscripts\smoke.py --mongod="c:\Program Files\MongoDB 2.5.2 Enterprise\bin\mongod.exe" --mongo="c:\Program Files\MongoDB 2.5.2 Enterprise\bin\mongo.exe" --smoke-db-prefix=d:\smoke --use-ssl --use-x509 sharding

Participants:

 Description   

Line 568 in src\mongo\shell\servers.js

resetDbpath( opts.dbpath )

causes the smoke-db-prefix path to be overriden. In this case the server did not have c:\data\db and it caused the test to fail.



 Comments   
Comment by Kyle Erf [ 23/Oct/13 ]

Duplicate of SERVER-9579

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