Fix test-aws-lambda-deployed cluster connection timeout

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Duplicate
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Go Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Name of Failure:

      The "test-aws-lambda-deployed" task 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.

      after the Atlas cluster creation succeeds.

      Link to task:

      https://spruce.mongodb.com/task/mongo_go_driver_faas_test__version~7.0_os_faas_80~rhel87_large_test_aws_lambda_deployed_910eb268789a1e9821525b5ec233f90c694fb049_25_08_06_19_08_34/logs?execution=1

      Context of when and why the failure occurred:

      The test fails after the Atlas cluster is successfully created and while attempting to check connectivity. The task passes if an "allow all traffic" network rule is added, but does not pass if the Evergreen-specific IP address ranges are allowed.

      Stack trace:

      Installing MongoDB shell... done.
MongoDB shell version: 2.5.6
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.
/data/mci/e20425463889da33ffff1f804085a92e/src/go.mongodb.org/mongo-driver
Command 'subprocess.exec' (step 3 of 3) in block 'setup_group' failed: process encountered problem: exit code 1.
Finished command 'subprocess.exec' (step 3 of 3) in block 'setup_group' in 10m29.929243069s.

              Assignee:
              Matt Dale
              Reporter:
              Matt Dale
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: