[SERVER-47822] Re-enable sharding multiversion suites Created: 28/Apr/20  Updated: 29/Oct/23  Resolved: 13/May/20

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

Type: Task Priority: Major - P3
Reporter: Jason Chan Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47911 Prevent stale_mongos_and_restarted_sh... Closed
is depended on by SERVER-42982 Unblacklist multiVersion/upgrade_down... Closed
Related
related to SERVER-47093 Re-enable multiversion passthroughs Closed
related to SERVER-48192 investigate the failures in the targe... Closed
related to SERVER-49413 Re-enable tests in multiversion suite... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-18
Participants:

 Description   

SERVER-47093 will re-enable all multiversion passthroughs except for the sharding ones as there some test failures that still need to be looked at



 Comments   
Comment by Kaloian Manassiev [ 27/May/20 ]

Commit: https://github.com/mongodb/mongo/commit/4f4cc93acec2a7e8d33534ee2b7d70e8203f4a21#diff-d420e7e0de06e336a85b31adadc62780

Comment by Kaloian Manassiev [ 12/May/20 ]

Per discussion with blake.oler and max.hirschhorn, the plan for enabling the Sharded multiversion suites will look like this:

  1. Owner blake.oler: Under the scope of this ticket, enable all the blacklisted Sharding multiversion suites without actually investigating any of the failures. Any failing tests will be blanket-disabled with the need_fixing_for_46 tag. Once this is committed, this ticket is done and can be closed.
  2. Owner kaloian.manassiev: Create a BF or SERVER ticket for each usage of need_fixing_for_46 and assign them to people in the Sharding Team.
  3. Owner backlog-server-sharding: Work through the generated BF and SERVER tickets with the highest priority over non-4.4 project work.

Estimated time to complete this work is 2 iterations, counting from today, so realistically, 9 June.

Comment by Blake Oler [ 08/May/20 ]

To whoever picks this up (CC kaloian.manassiev), I did a test patch of re-enabling all of the above suites. It looks like a lot of them are already green. Hopefully this will save you some time!

Comment by Jason Chan [ 29/Apr/20 ]

As part of this ticket, we should also investigate the failures in the targeted multiversion tests for pending_chunk.js and migrations_with_mixed_fcv.js.

Once these failures are resolved, we can unblacklist them from the multiversion.yml and multiversion_auth.yml suite config files.

Comment by Jason Chan [ 29/Apr/20 ]

To enable the sharding passthroughs we should do the following:

  • Uncomment the following for change_streams_sharded_collections_multiversion_passthrough here and here
  • Uncomment the following for sharding_multiversion_gen here
  • Uncomment the following for sharded_collections_jscore_multiversion_passthrough_gen here and here
  • Uncomment the following for sharding_jscore_multiversion_passthrough_gen here and here
  • Uncomment the following for concurrency_sharded_replication_multiversion_gen here and here
  • Uncomment the following buildscripts tests in test_burn_in_multiversion_tests.py here and here
Generated at Thu Feb 08 05:15:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.