[SERVER-66008] cluster.js calls an undefined function to iterate over the config server nodes Created: 27/Apr/22  Updated: 29/Oct/23  Resolved: 28/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
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: Sharding EMEA 2022-05-02
Participants:
Linked BF Score: 0

 Description   

SERVER-58683 changed the way cluster.js iterates through the nodes of the config server replica set to perform several operations (such as executeOnConfigNodes()) by relying on the st.forEachConfigServer function.
 
Nevertheless, such function is undefined in Cluster.st, which is an object of type FSMShardingTest (and not ShardingTest).

(The consequences of this may go unperceived when executeOnConfigNodes() gets invoked in the setup() of an FSM workload: an uncaught exception will appear in the test log and no operation will be applied to the config server nodes, but the workload itself will be executed anyway, and possibly pass the test assertions).



 Comments   
Comment by Githook User [ 03/May/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-66008 fix undefined function bug in cluster.js

(cherry picked from commit 782e90f7ae48b583c0a33d555286ef035f35e396)
Branch: v6.0
https://github.com/mongodb/mongo/commit/5b1fe61d1a2f19cce13e362b42b97ed3495976eb

Comment by Githook User [ 28/Apr/22 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-66008 fix undefined function bug in cluster.js
Branch: master
https://github.com/mongodb/mongo/commit/782e90f7ae48b583c0a33d555286ef035f35e396

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