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

[RN 2.0.1] Online upgrade(2.0->2.0.1) for a node referenced with hostname causes it to be referenced by ip again

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • 2.0.1
    • 2.0, 2.0.1
    • installer, tools
    • Security Level: Public
    • Release Note

    Description

      Online upgrade(2.0->2.0.1) for a node referenced with hostname causes it to be referenced by ip again. Though ip file correctly shows the hostname.

      The same case works fine for offline upgrade.

      Scenario:

      • Create a 2.0 cluster of 2 nodes (both nodes referenced with hostname, couchbase-server/ip file updated with hostname)
        N1 - ec2-54-251-74-125.ap-southeast-1.compute.amazonaws.com
        N2 - ec2-54-251-92-43.ap-southeast-1.compute.amazonaws.com
      • Create 1 default bucket, load gamesim-sample bucket
      • Rebalance out N2
      • Upgrade the node N2 (rpm -U couchbase-server...) [build 2.0.1-145-rel]
      • Add node N2 back to cluster again using hostname while adding node. Rebalance.
      • Node N2 is now shown being referenced by IP address rather than hostname.

      The live cluster:
      http://ec2-54-251-74-125.ap-southeast-1.compute.amazonaws.com:8091

      Access:
      ssh -i SingaporeQAkey.pem ec2-user@ec2-54-251-74-125.ap-southeast-1.compute.amazonaws.com

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            kzeller kzeller
            deepkaran.salooja Deepkaran Salooja
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty