[SERVER-42982] Unblacklist multiVersion/upgrade_downgrade_cluster.js Created: 22/Aug/19  Updated: 29/Oct/23  Resolved: 17/Jun/20

Status: Closed
Project: Core Server
Component/s: Sharding, Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-43849 Write NotMaster error in upgrade_down... Closed
depends on SERVER-47822 Re-enable sharding multiversion suites Closed
is depended on by SERVER-43852 Make upgrade_downgrade_cluster.js sta... Closed
Related
is related to SERVER-42919 Abort mongos upon IncompatibleWithUpg... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-09-23, Sharding 2019-10-07, Sharding 2019-10-21, Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13, Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23, Sharding 2020-04-06, Sharding 2020-04-20, Sharding 2020-06-15, Sharding 2020-06-29
Participants:

 Comments   
Comment by Githook User [ 16/Jun/20 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}

Message: SERVER-42982 unblacklist upgrade_downgrade_cluster test from multiversion suites
Branch: master
https://github.com/mongodb/mongo/commit/fb777a1aa5d7e9c238e3905e51bc13e924c234bb

Comment by Misha Tyulenev [ 22/Apr/20 ]

This test cannot be unblacklisted from master until last-stable FCV becomes 4.4 because of the refineShardKey _id format error
below:

Failed to handle stale version exception as part of the current
operation{"error":"TypeMismatch: Failed to parse chunk with id _id:
\"sharded.foo-x_MinKey\" :: caused by :: \"_id\" had the wrong type. Expected
objectId, found string"}

According to jack.mulrow, we changed the format of config.chunks documents between 4.2
and 4.4 and used to convert between the formats as part of
setFeatureCompatibilityVersion but this logic does not exist in master. The test
is failing because the last-stable FCV is still 4.2, so even though our mixed
binary tests start with both 4.4 binaries, they use the 4.2 FCV behavior.

Comment by Githook User [ 04/Oct/19 ]

Author:

{'email': 'misha.tyulenev@10gen.com', 'name': 'Misha Tyulenev'}

Message: Revert "SERVER-42982 unblacklist multiVersion/upgrade_downgrade_cluster.js"
Branch: master
https://github.com/mongodb/mongo/commit/ef04738ab1e3a0a5c8ad7f915a401f2e754d5126

Comment by Githook User [ 03/Oct/19 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha.tyulenev@10gen.com'}

Message: SERVER-42982 unblacklist multiVersion/upgrade_downgrade_cluster.js
Branch: master
https://github.com/mongodb/mongo/commit/aa2ccf6e1992b41ac1b286291e6217d91157f573

Generated at Thu Feb 08 05:01:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.