[SERVER-64479] Fix LDAP firewall concurrency issue Created: 14/Mar/22  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Witten (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-64367 Replace ufw firewall with port specif... Closed
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:
Linked BF Score: 39
Story Points: 2

 Description   

As part of the external_auth.yml suite, the test "ldap_mongos_health_checking_crash.js" enables a firewall between the mongos and the ldap server. This firewall is only enabled on linux. If this test runs concurrently with tests that require being able to talk to the LDAP server, those tests will fail. As part of SERVER-64322, concurrency in the external_auth.yml test suite was disabled. We would like to eventually enable it again. When that happens, there will be failures and this issue will need to be addressed.



 Comments   
Comment by Andrew Witten (Inactive) [ 14/Mar/22 ]

This might fix the issue for us: https://stackoverflow.com/a/28074580/11764841. Adding this to the JS directly.

Comment by Andrew Witten (Inactive) [ 14/Mar/22 ]

Ticket SERVER-64367 addressed a different issue which is that ufw doesn't work for the purposes of these tests cases.

Comment by Andrew Witten (Inactive) [ 14/Mar/22 ]

This is only for linux. Unrelated to the windows concurrency issues, we have jstests ldap_mongos_health_checking_crash.js and ldap_mongos_health_checking.js which, only on linux, enable a firewall to the ldap server. This will cause issues for the other ldap tests once we enable concurrency again.

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