[SERVER-67324] Replace calls to replSetStepUp in jstest with stepUp in tenant_migration_recipient_access_blocker_rollback.js Created: 15/Jun/22  Updated: 29/Oct/23  Resolved: 27/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0, 6.1.1, 6.0.3, 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Mathis Bessa Assignee: Adi Agrawal
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-67194 Replace the logic in our jstest to re... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.1, v6.0
Participants:
Linked BF Score: 0

 Description   

The tenant_migration_recipient_access_blocker_rollback.js still uses the old replSetStepUp command instead of calling the replSetTest.stepUp method.

We should replace in this test file all occurrences to instead use the stepUp method.

Note: It was found during a previous investigation that replacing this line in the test by stepUp might hang when we call getPrimary in the stepUp method.



 Comments   
Comment by Githook User [ 06/Oct/22 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'aa729@cornell.edu', 'username': 'Adityav369'}

Message: SERVER-67324: wrap replSetSetup cmd in assert.soon
Branch: v6.0
https://github.com/mongodb/mongo/commit/5797fb0282b1b08328b375343125443256a11402

Comment by Githook User [ 05/Oct/22 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'aa729@cornell.edu', 'username': 'Adityav369'}

Message: SERVER-67324: wrap replSetSetup cmd in assert.soon
Branch: v6.1
https://github.com/mongodb/mongo/commit/8062f490260eac573ad48915b5d8ccc478bb5b9a

Comment by Githook User [ 27/Sep/22 ]

Author:

{'name': 'Adityavardhan Agrawal', 'email': 'aa729@cornell.edu', 'username': 'Adityav369'}

Message: SERVER-67324: wrap replSetSetup cmd in assert.soon
Branch: master
https://github.com/mongodb/mongo/commit/2371fd2f3f37c26ba1b0d83db0f7f716042df2f6

Comment by Steven Vannelli [ 27/Jun/22 ]

Not enough a priority at this point but if this surfaces as an issue, we can reopen.

Generated at Thu Feb 08 06:07:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.