Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-3083

Astrolabe: Cluster Setup Failure due to TLS versioning

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Component/s: Astrolabe, Atlas Testing
    • None
    • Not Needed

      Summary

      Since Jan 8, the following test cases have setup failures on drivers-atlas-testing for all drivers:

      • retryReads processRestart
      • retryReads processRestart-sharded

      It looks like the root cause is the TLS_CONFIGURATION being on a version lower than 1.2.

      This issue is likely due to the Atlas upgrade to openssl 3, which by default requires a TLS minimum of TLSv1.2

      Motivation

      Who is the affected end user?

      Atlas users

      How does this affect the end user?

      Unknown, it's unlikely users themselves are on TLS versions < 1.0, but it's possible whatever is awry in our configuration could also affect them.

      How likely is it that this problem or use case will occur?

      Unknown

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      N/A

      Is this ticket required by a downstream team?

      No

      Is this ticket only for tests?

      Potentially yes, depending on the outcome of the ticket.

      Acceptance Criteria

      Investigate cause of build failure / why it started occurring

            Assignee:
            matt.dale@mongodb.com Matt Dale
            Reporter:
            aditi.khare@mongodb.com Aditi Khare (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: