-
Type:
Build Failure
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
Go Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Name of Failure:
The "test-aws-lambda-deployed" task always fails with an error like
MongoServerSelectionError: Server selection timed out after 30000 ms. It looks like this is a MongoDB Atlas cluster. Please ensure that your Network Access List allows connections from your IP.
Link to task:
Context of when and why the failure occurred:
The failure occurs consistently. Temporarily setting an "allow all traffic" rule to the "go" Atlas project network config allows the task to pass, suggesting it's related to the Atlas firewall config.
Stack trace:
Checking every 15 seconds for deployment to be created... {"advancedConfiguration":{"customOpensslCipherConfigTls12":[],"minimumEnabledTlsProtocol":"TLS1_2","tlsCipherConfigMode":"DEFAULT"},... Waiting for Deployment dbx-go-lambda-9a87d9764ee6e304 in Group 5e3875b7f2a30b07ca1ebae1... done. ... MongoServerSelectionError: Server selection timed out after 30000 ms. It looks like this is a MongoDB Atlas cluster. Please ensure that your Network Access List allows connections from your IP. Command 'subprocess.exec' (step 3 of 3) in block 'setup_group' failed: process encountered problem: exit code 1.
- is depended on by
-
GODRIVER-3626 Release Go Driver 2.3.0
-
- In Progress
-
- is duplicated by
-
GODRIVER-3636 Fix test-aws-lambda-deployed cluster connection timeout
-
- Closed
-