[CDRIVER-2327] Replica set auth tests not running Created: 13/Oct/17  Updated: 28/Oct/23  Resolved: 09/Nov/17

Status: Closed
Project: C Driver
Component/s: tests
Affects Version/s: None
Fix Version/s: 1.9.0

Type: Bug Priority: Major - P3
Reporter: Kevin Albertson Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When running patch builds with new tests, I found what looks to be a failure in replica set auth tests (on master, with no code changes):

https://evergreen.mongodb.com/version/59e0c3e32fbabe44f60068e2

The failure is in the test Client/authenticate_cached/pool with the error:

tests/test-mongoc-client.c:474 test_mongoc_client_authenticate_cached(): testing The cachekey broke didn't log "Failed authentication"

We didn't run into this because no replica set tests with auth are being run, even though we have the tasks defined. Maybe I'm missing something, and those tests were removed intentionally? If so, then we should remove them from config.yml. Otherwise, that test failure may be legitimate.

FYI reproducing this locally may be a little annoying, since mlaunch has an open bug when creating replica-sets with auth



 Comments   
Comment by A. Jesse Jiryu Davis [ 09/Nov/17 ]

The test failure was due, I think, to a mistaken assumption that the primary always had server id 1 in the internal topology data structure.

Comment by Githook User [ 09/Nov/17 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}

Message: CDRIVER-2327 use primary's server id in auth test
Branch: master
https://github.com/mongodb/mongo-c-driver/commit/aa11151f2dc6d48da1a8dc95afc7eee783874200

Comment by Githook User [ 09/Nov/17 ]

Author:

{'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis', 'email': 'jesse@mongodb.com'}

Message: CDRIVER-2327 enable replicaset auth tests
Branch: master
https://github.com/mongodb/mongo-c-driver/commit/7cf6ab10c28f27bde67c9fb22cdf66ae060f9a9e

Comment by Kevin Albertson [ 17/Oct/17 ]

In addition, this may also be true of all 2.6 auth tests. Some new valgrind tests failed with the same error message on a patch build:
this task and this one

The corresponding (non-valgrind) tasks (test-valgrind-2.6-sharded-auth-nosasl-openssl and test-valgrind-2.6-server-auth-nosasl-openssl) don't seem to get scheduled.

Generated at Wed Feb 07 21:14:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.