Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-40307

ssl_cluster_ca.js and ssl_hostname_validation.js time out

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • 0

      The SSL tests that validate that replica sets cannot form with invalid SSL certificates are timing out after SERVER-40060.

      The retry logic I added to ReplSetTest.initiate() in that ticket has a bug: if replSetInitiate or replSetReconfig fails with one of the expected error codes then ReplSetTest considers that success, and doesn't retry the command. In the SSL tests ssl_cluster_ca.js and ssl_hostname_validation.js, replSetReconfig fails with NodeNotFound (because the test deliberately misconfigures TLS) but ReplSetTest considers that a success, and moves to the next stage of ReplSetTest.initiate, which is awaitSecondaries(). That takes 5 minutes to fail. Once it finally does fail, ssl_cluster_ca.js or ssl_hostname_validation.js considers that failure expected, and moves on.

      Since there are multiple such calls to ReplSetTest.initiate in each of these jsTests, they hit their Evergreen task timeout before they finish.

            Assignee:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: