[SERVER-7356] Make disk tests pass with auth Created: 15/Oct/12  Updated: 10/Sep/18  Resolved: 10/Sep/18

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-7357 Clean up how the shell launches proce... Closed
is depended on by SERVER-4237 Enable the full js test suite to run ... Closed
Duplicate
is duplicated by SERVER-7351 Command line parsing error -- 'mongod... Closed
Related
related to SERVER-7317 Make dur tests pass with auth Closed
related to SERVER-13194 Make remaining test suites run in aut... Closed
Participants:

 Description   

Currently disk/repair.js fails when running with auth because it uses runMongoProgram to start a mongod so that they can get the return code when the process finishes. The problem is that when in auth mode runMongoProgram adds a -u and -p argument to allow tools that are started that way to connect to mongods running with auth, but mongod doesn't have a -u or -p argument.
The ideal fix would be to use startMongodTest which does the right thing with auth, but startMongodTest doesn't currently provide any way to check the return code of the mongod process when it terminates.

To fix this we should add a way to join() to a mongod process started with startMongodTest and get it's return code. Then we can change all disk and dur tests to use startMongodTest instead of runMongoProgram and can get the exit status that way.



 Comments   
Comment by auto [ 15/Oct/12 ]

Author:

{u'date': u'2012-10-15T08:26:29-07:00', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}

Message: SERVER-7356 SERVER-4237 Skip disk tests when running with auth
Branch: master
https://github.com/mongodb/mongo/commit/3342a6ec9cb3a79794587c8d2927257617fbf60d

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