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

In external_auth_WT JSTests, ensure that Saslauthd has fully started before continuing test

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.14, 4.1.12, 4.0.11
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Security 2019-05-06, Security 2019-05-20
    • Linked BF Score:
      50

      Description

      In the test framework, because we're managing the lifecycle of external processes we're dependent on, it seems like it is possible to start saslauthd, but for saslauthd to not have fully started by the time MongoDB has started. To fix this, we should use runProgram, which will return once saslauthd has doubleforked, instead of _startMongoProgram which returns immediately. Then, we should repeatedly check for the existence of saslauthd's socket file. If the socket file exists, we have a good guarantee that saslauthd is running.

        Attachments

          Activity

            People

            Assignee:
            jonathan.reams Jonathan Reams
            Reporter:
            spencer.jackson Spencer Jackson
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: