[SERVER-14312] avoid attempting to reconfig before node 3 comes back online in reconfig.js Created: 19/Jun/14  Updated: 11/Jul/16  Resolved: 19/Jun/14

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 2.7.2
Fix Version/s: 2.7.3

Type: Improvement Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Linked BF Score: 0

 Description   

this is the cause of much of the flakiness in the test



 Comments   
Comment by Githook User [ 20/Jun/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-14312 ensure node 0 will be primary as part of the reconfig.js fix
Branch: master
https://github.com/mongodb/mongo/commit/d7b4f787b0c2885ba80f76a54a4961a32ee1debf

Comment by Githook User [ 19/Jun/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-14312 fix a failure mode of reconfig.js
Branch: master
https://github.com/mongodb/mongo/commit/629f77c7b5979216f36840153d67eaa8a60082bc

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