-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
v9.0
-
CAR Team 2026-10-26, CAR Team 2026-11-09
-
None
-
None
-
None
-
None
-
None
-
None
-
None
chunk_migration_does_not_block_indefinitely_acquiring_strong_locks.js coordinator-warning assertion fails in the 9.0 sharding_last_patch suite when the donor runs 9.0.4. In particular, the migration correctly returns LockTimeout, and writes complete successfully. However, 9.0.4 logs the coordinator failure as error 7524000, while the test expects warning 13580300, introduced by the logging fix in SERVER-136085. On the v9.0 branch, last-LTS is 8.0, so the assertion still runs against 9.0.4 skipping the current last-LTS exclusion.
As part of this ticket, we should preserve the last-LTS exclusion while adding a skip when useRandomBinVersionsWithinReplicaSet is "last-patch".