[SERVER-78757] Make cluster_time_across_add_shard.js run correctly in sharding_last_lts_mongos_and_mixed_shards suite with config shard enabled Created: 07/Jul/23  Updated: 29/Oct/23  Resolved: 07/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc7

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
Participants:
Linked BF Score: 60

 Description   

When running with config shard enabled, this test starts a sharded cluster by manually starting a mongos and connecting it to the configsvr replset (here). When running in a mixed version suite, to allow the mongos to connect to the configsvr, the test needs to run a setFCV command against the configsvr to downgrade the FCV to 7.0, just like what ShardingTest does.

This test should be disabled from sharding_last_lts_mongos_and_mixed_shards the config shard variant, since it involves running a transitionFromDedicatedConfigServer command which doesn't exist prior to 7.0.



 Comments   
Comment by Githook User [ 07/Jul/23 ]

Author:

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

Message: SERVER-78757 Make cluster_time_across_add_shard.js run correctly in sharding_last_lts_mongos_and_mixed_shards suite with config shard enabled
Branch: master
https://github.com/mongodb/mongo/commit/c491bc4f08000b816f69c3eaa796424e4e78875c

Comment by Githook User [ 07/Jul/23 ]

Author:

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

Message: SERVER-78757 Disable cluster_time_across_add_shard.js in sharding_last_lts_mongos_and_mixed_shards suite on config shard variant
Branch: v7.0
https://github.com/mongodb/mongo/commit/c8002e9f12995ae16d510778aacde822be081b48

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