Better instrumentation for TLS authentication problem during concurrent tenant migration

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.1.0-rc0
    • Affects Version/s: 5.0.0
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Hide

      Failure from BF-21501

       

      Show
      Failure from BF-21501  
    • Core Eng TPM 2021-07-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a race somewhere in TLS authentication during many concurrent tenant migrations. The recipient d20522 does not match the name coming with cert from the donor:

       

      d20522| 2021-06-10T03:12:12.909+00:00 I  ACCESS   5286202 [conn16] "Different user name was supplied to saslSupportedMechs","attr":{"error":{"code":17,"codeName":"ProtocolError","errmsg":"Attempt to switch user during SASL authentication."}}

      Need better logging in the chain, then will wait for it to happen again.

              Assignee:
              Andrew Shuvalov (Inactive)
              Reporter:
              Andrew Shuvalov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: