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

ensure cause is clear when jstests user_defined_roles_on_secondaries.js fails

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • None
    • Security
    • None
    • Fully Compatible
    • ALL
    • Security 2021-04-19
    • 147

    Description

      in BF-20634 we have an unclear cause of failure. It could be one of:

      • dropRole could have failed, and since we are not checking result we can't tell it didn't
      • call could have returned before replication completed, and since we are not checking primary first, we can't tell it's not the case

      I am making an attempt to reproduce an issue on windows/debug, so far without success.

      After discussion with xuerui.fa we decided following needs to be done:

      • check that dropRole succeeds
      • check that after dropRole succeeds, the role has indeed disappeared from primary before checking all other nodes

      This will not address the root cause, but will help eliminate possibilities

      Attachments

        Activity

          People

            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: