[SERVER-83415] Make cluster_cardinality_parameter.js only assert the "hasTwoOrMoreShards" is wrong when the cluster is upgrading from "last-lts" Created: 17/Nov/23  Updated: 20/Nov/23  Resolved: 20/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Cluster Scalability 2023-11-27
Participants:
Linked BF Score: 70

 Description   

7.3 contains the fix in SERVER-81974 and is becoming "last-continous" (it already is in the multiversion_future_git_tag suite). So it's incorrect to always assert that "hasTwoOrMoreShards" is wrong when the cluster is upgrading from "last-continous".  



 Comments   
Comment by Githook User [ 20/Nov/23 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-83415 Make cluster_cardinality_parameter.js only assert the hasTwoOrMoreShards is wrong when the cluster is upgrading from 'last-lts'
Branch: master
https://github.com/mongodb/mongo/commit/084ff6c169a8c00e9037b21ee1677cb7ed03077d

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