[SERVER-67846] Tests relying on featureFlagCollModIndexUnique should check FCV 60 Created: 07/Jul/22  Updated: 29/Oct/23  Resolved: 03/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.2, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Execution Team 2022-08-08
Participants:
Linked BF Score: 5

 Description   

Tests skip running (example) if featureFlagCollModIndexUnique is disabled (checked with getParam), and some of those tests have a 'requires_fcv_52' tag or no FCV tag, but the feature flag is FCV 60.

This causes the tests to run because getParam returns true, but later fail because the feature flag is actually disabled by the isEnabled FCV check.

For instance, tests may fail due to "collMod does not support converting an index to 'unique' or to 'prepareUnique' mode".

Tests should make sure the FCV is 60, for instance by updating tags to requires_fcv_60 or explicitly checking the FCV together with getParam. 

 



 Comments   
Comment by Githook User [ 05/Sep/22 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-67846 Add requires_fcv_60 tag to tests querying featureFlagCollModIndexUnique

(cherry picked from commit 4dcb8f0e5565b6b2fea8d467e4c3f436363d0cc5)
Branch: v6.0
https://github.com/mongodb/mongo/commit/9cf479fb3684c22ef55bbce90a9cfce46297cfa6

Comment by Githook User [ 03/Aug/22 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-67846 Add requires_fcv_60 tag to tests querying featureFlagCollModIndexUnique
Branch: master
https://github.com/mongodb/mongo/commit/4dcb8f0e5565b6b2fea8d467e4c3f436363d0cc5

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