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

Make shell dbHash comparison to exclude encryption options

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.0.12, 5.0.28, 6.0.17
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0, v6.0, v5.0
    • Execution EMEA Team 2023-10-30
    • 40

      SERVER-68122 introduced a change that makes secondaries not replicate into the durable catalog any encryption option passed to the primary. This was intended, as it served as a way to avoid crashes due to non-existent encryption keys.

      However, SERVER-79496 banned the option altogether and introduced a new test to this effect. This test is now being used in the fuzzer and causes dbHash mismatches in the shell since nodes do not have the same collection config metadata across nodes.

      We are already doing some collection info manipulation today to avoid getting false-positives during testing here. We should consider scrubbing the encryption options from testing as well since we are deliberately allowing them to differ across nodes now.

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: