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

Use failpoints to exercise audit log rotation failure on startup

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.2, 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      Enterprise RHEL 8.1 PPC64LE, Enterprise macOS
    • Fully Compatible
    • v5.3
    • Security 2022-03-21, Security 2022-04-04
    • 152

      Currently src/mongo/db/modules/enterprise/jstests/audit/log_rotate_startup.js consistently fails on Enterprise RHEL 8.1 PPC64LE and **Enterprise macOS , because the javascript test runners use GMT-5 (local timezone) on these variants when generating test file names for causing collisions with rotating audit log files, instead of the GMT-0 used by all other tested variants.

      The test consistently fails because mongod uses GMT-0 when it rotates files, thus for these two variants, there is never a collision, the server starts normally and the test fails.

      To correct this failing test and prevent further false-negatives we can use failpoints to test audit log rotation failing at various points in the process instead of relying on the variable external environment.

            Assignee:
            adam.rayner@mongodb.com Adam Rayner
            Reporter:
            adam.rayner@mongodb.com Adam Rayner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: