Couchbase .NET client libraryIcon indicating the project type

Couchbase .NET client library

Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1496

Memcached bucket integration tests fail

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.4.8
    • Fix Version/s: 2.5.0
    • Component/s: None
    • Labels:
      None

      Description

      Unable to run any memcahced bucket tests:
      MemcachedBucketTests
      MemcachedBucketTests_Isolated

      Also seems to affect:
      MemcachedBucketManagerTests

        Attachments

          Issue Links

          is caused by

          Improvement - An improvement or enhancement to an existing feature or task. NCBC-1479 Update test projects so that we can toggle between RBAC and older auth modes

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved
          For Gerrit Dashboard: NCBC-1496
          # Subject Branch Project Status CR V
          82981,2 NCBC-1496: Memcached bucket integration tests fail master couchbase-net-client Status: MERGED +2 +1

            Activity

            Hide
            Permalink
            jmorris Jeff Morris added a comment -

            There is a bug that for every nth+1 node that is initialized the bucketname is passed into authenticate (ScramShaMechanism) instead of the username. If you test on a single node cluster it will appear to work fine, if you add a node you will see initialization fail for each additional node and the client will return NodeUnavailableException, which will never resolve.

            Show
            jmorris Jeff Morris added a comment - There is a bug that for every nth+1 node that is initialized the bucketname is passed into authenticate (ScramShaMechanism) instead of the username. If you test on a single node cluster it will appear to work fine, if you add a node you will see initialization fail for each additional node and the client will return NodeUnavailableException, which will never resolve.

              People

              • Assignee:
                jmorris Jeff Morris
                Reporter:
                mike.goldsmith Michael Goldsmith
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.