Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-19972

When configuring server, error message affects "Next" button when it shouldn't

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 4.6.0
    • 4.5.0
    • UI
    • Security Level: Public
    • I'm using Windows, but my guess is this is an issue cross-platform.

      I'm using Enterprise Edition of 4.5 (whatever build is on Docker hub as of right now)
    • Untriaged
    • Unknown

    Description

      Summary: When trying to "Join a cluster now", if there is an error in the "Start a new cluster" section, then I can't click "Next".

      Repro:
      1. Install Couchbase server, go to Step 1 of 5 in Setup
      2. Select "Start a new cluster".
      3. Enter some RAM quota that is too high. For instance, if RAM available is 1998 MB, then enter a Data RAM Quote of 2056.
      4. Note that the "Next" button cannot be click.
      5. Now select "Join a cluster now"
      6. Notice that the "Next" button still cannot be clicked.
      7. Switch back to "Start a new cluster"
      8. Change the RAM quota so that the error message goes away (e.g. enter a low Data RAM quota value)
      9. Notice that the "Next" button can be clicked now.
      10. Select "Join a cluster now"
      11. "Next" can still be clicked.

      Expected:
      The values in "Start a new cluster" should have no effect on the "Next" button when "Join a cluster now" is selected.

      Actual:
      The "Next" button is controlled by "Start a new cluster" validation even if "Join a cluster now" is selected.

      I attached an animated GIF of the behavior. I also attached a Fiddler trace just in case.

      Attachments

        Issue Links

          Activity

            People

              pavel Pavel Blagodov
              matthew.groves Matthew Groves
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty