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

[windows] unable to upgrade failed over node on destination cluster

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.1
    • Component/s: installer
    • Security Level: Public
    • Labels:
      None
    • Environment:
    • Sprint:
      PCI Team - Sprint 1

      Description

      unidirectional xdcr/2 clusters/ 4 nodes each cluster
      source cluster : 2.0.1-156-rel on all nodes
      destination cluster: 3 nodes have 2.0.1-156-rel, 1 is of 2.0.0-1976-rel.

      Stopped couchbase service on 2.0.0-1976-rel node.
      Failed over it (not rebalanced)
      Tried to run 2.0.1 installer. error message appears about user cannot upgrade couchbase server because some other process is using files.
      I killed firefox and cmd processes on the node and tried to run installer again
      Message that couchbase server will be updated appeared and i chose ok -> couchbase server is uninstalled, new version is not installed.all data is lost

      back up from this node is attached

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

        Activity

        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Bin,

        all logs are also attached there.

        Iryna,
        is the vm still in that state ?

        Show
        farshid Farshid Ghods (Inactive) added a comment - Bin, all logs are also attached there. Iryna, is the vm still in that state ?
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        assigning this to Bin since its a windows upgrade issue

        Show
        farshid Farshid Ghods (Inactive) added a comment - assigning this to Bin since its a windows upgrade issue
        Hide
        bcui Bin Cui (Inactive) added a comment -

        I cannot reproduce the bug on my test vm 10.3.121.181 when upgrading 2.0.0-1976-rel to 2.0.1-156-rel.

        Based on description, i suspect the failure is caused by corrupted registry keys on that vm. And the attached logs don't provide anything related to installation.

        What if you uninstall everything first, install 2.0.0 and populate some day and upgrade again? And when upgrading, specify commands such as:
        setup.exe /debuglog"C:\PathToLog\setupexe.log"

        In this way, we can find out what's wrong during upgrade.

        Show
        bcui Bin Cui (Inactive) added a comment - I cannot reproduce the bug on my test vm 10.3.121.181 when upgrading 2.0.0-1976-rel to 2.0.1-156-rel. Based on description, i suspect the failure is caused by corrupted registry keys on that vm. And the attached logs don't provide anything related to installation. What if you uninstall everything first, install 2.0.0 and populate some day and upgrade again? And when upgrading, specify commands such as: setup.exe /debuglog"C:\PathToLog\setupexe.log" In this way, we can find out what's wrong during upgrade.

          People

          • Assignee:
            bcui Bin Cui (Inactive)
            Reporter:
            iryna iryna
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile

                Gerrit Reviews

                There are no open Gerrit changes