Update initial DNS seedlist discovery tests to support dedicated load balancer port

XMLWordPrintableJSON

    • Needed
    • Hide

      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver.

      Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID.

      Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668
      Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148
      Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861

      Show
      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver. Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID. Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668 Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148 Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-4302 Gone away
      CXX-2460 Won't Do
      CSHARP-4084 Fixed 2.16.0
      GODRIVER-2324 Done
      JAVA-4513 Backlog
      NODE-4057 Done
      MOTOR-903 Duplicate
      PYTHON-3153 Fixed 4.2
      PHPLIB-805 Won't Do
      RUBY-2915 Backlog
      RUST-1202 Fixed 2.2.0
      SWIFT-1507 Fixed 1.3.0
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } #scriptField td.willNotDo { background-color: #FF0000; /* Red color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-4302 Gone away CXX-2460 Won't Do CSHARP-4084 Fixed 2.16.0 GODRIVER-2324 Done JAVA-4513 Backlog NODE-4057 Done MOTOR-903 Duplicate PYTHON-3153 Fixed 4.2 PHPLIB-805 Won't Do RUBY-2915 Backlog RUST-1202 Fixed 2.2.0 SWIFT-1507 Fixed 1.3.0

      Summary

      The driver updates required in DRIVERS-1983 break the initial-dns-seedlist-discovery load-balanced tests because those tests still point the driver directly at the mongos instances, requiring that the driver still mocks the service ID. See this comment for more details about the test failures in the Go driver.

      Update those tests and the associated DNS records to point the driver at the load balancer started by run-load-balancer.sh, allowing drivers to stop mocking service ID.

      Here's the ticket for updating the DNS records: https://jira.mongodb.org/browse/BUILD-14668
      Here's a PR for the test changes: https://github.com/mongodb/specifications/pull/1148
      Here's the draft PR testing the spec test changes in the Go driver: https://github.com/mongodb/mongo-go-driver/pull/861

      Motivation

      Who is the affected end user?

      Driver devs implementing the changes required by DRIVERS-1983.

      How does this affect the end user?

      The initial DNS seedlist discovery spec tests fail.

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

      The test failures will always happen after doing the driver changes required by DRIVERS-1983.

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

      Driver devs will have to investigate unexplained test failures.

      Is this issue urgent?

      No.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Yes.

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

              Created:
              Updated: