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

Upgrade : Windows offline upgrade from 5.0.1 to 5.5 not working

    XMLWordPrintable

    Details

    • Triage:
      Untriaged
    • Story Points:
      2
    • Is this a Regression?:
      Unknown
    • Sprint:
      Build Team 2018 Sprint 13, Build Team 2018 Sprint 15, Build Team 2018 Sprint 16

      Description

      Build : 5.5.0-2928

      During Spock release, since there was a change in the installer packaging for Windows from exe to MSI, offline upgrade was not possible. But now since 5.0.1 and 5.5.0 both uses the MSI based installer, offline upgrade should work. Currently it is not working. The installer rolls back the actions taken and the summary screen as attached is shown.

      Release note for 5.0.0 contained this :
      For Windows, .exe installers which were previously deprecated are now removed and replaced with industry-standard MSI installer files. Consequently, any upgrade for the Windows platform from pre-5.0 version to 5.0 will need to be done in a rolling upgrade fashion. See Performing the Rolling Online Upgrade for details.
      https://developer.couchbase.com/documentation/server/5.0/release-notes/relnotes.html

        Attachments

          Issue Links

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

            Activity

            Hide
            ceej Chris Hillery added a comment -

            Fix in 5.5.x, merged up to Alice and master. I've tested installing a locally-made 5.5.0 build with the change and then upgrading to 6.0.0, confirming that the data directory was left alone and the Server came up with the previously-defined cluster configuration. I also added a rollback step so the data is left untouched if there's an error during upgrade, and tested that.

            Show
            ceej Chris Hillery added a comment - Fix in 5.5.x, merged up to Alice and master. I've tested installing a locally-made 5.5.0 build with the change and then upgrading to 6.0.0, confirming that the data directory was left alone and the Server came up with the previously-defined cluster configuration. I also added a rollback step so the data is left untouched if there's an error during upgrade, and tested that.
            Hide
            build-team Couchbase Build Team added a comment -

            Build couchbase-server-5.5.2-3703 contains voltron commit 1603b82 with commit message:
            MB-30227: Backup/restore var dir when doing major upgrade on Windows

            Show
            build-team Couchbase Build Team added a comment - Build couchbase-server-5.5.2-3703 contains voltron commit 1603b82 with commit message: MB-30227 : Backup/restore var dir when doing major upgrade on Windows
            Hide
            thuan Thuan Nguyen added a comment -

            Successful offline upgrade 2 nodes cluster with services data, index and query from 5.5.2-3703 to 6.0.0-1620

            Show
            thuan Thuan Nguyen added a comment - Successful offline upgrade 2 nodes cluster with services data, index and query from 5.5.2-3703 to 6.0.0-1620
            Hide
            thuan Thuan Nguyen added a comment -

            Successful offline upgrade 2 nodes cluster with services data, index and query from 5.5.2-3703 to 6.5.0-1310.

            Show
            thuan Thuan Nguyen added a comment - Successful offline upgrade 2 nodes cluster with services data, index and query from 5.5.2-3703 to 6.5.0-1310.
            Hide
            lynn.straus Lynn Straus added a comment -

            reopened to remove 5.5.x candidate label as this is already fixed in 5.5.2.

            Show
            lynn.straus Lynn Straus added a comment - reopened to remove 5.5.x candidate label as this is already fixed in 5.5.2.

              People

              Assignee:
              mihir.kamdar Mihir Kamdar
              Reporter:
              mihir.kamdar Mihir Kamdar
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Gerrit Reviews

                  There are no open Gerrit changes

                    PagerDuty