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

offline upgrade failed when data folders have been removed. but as a result is new version was installed when start node manually

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0.1, 2.1.0
    • Fix Version/s: 3.0
    • Component/s: installer
    • Security Level: Public
    • Labels:
      None
    • Environment:
      ubuntu 32/64
      ran in windows by iryna (rc3), same. so not OS-specific bug.
      also reproduces for centos-32bit
    • Triage:
      Untriaged

      Description

      http://qa.hq.northscale.net/view/2.0.1/job/ubuntu-64-2.0-upgrade/82/consoleFull
      ./testrunner -i /tmp/upgrade.ini upgrade_version=2.0.1-150-rel,initial_vbuckets=64 -t newupgradetests.MultiNodesUpgradeTests.offline_cluster_upgrade_non_default_path,data_path=|tmp|data,index_path=|tmp|index,initial_version=2.0.0-1976-rel,items=10,nodes_init=3,num_nodes_remove_data=1,replicas=2

      steps:
      1. 3 nodes in cluster 2.0.0-1976-rel:
      for node 10.3.3.19 data paths are :data_path=/tmp/data,index_path=/tmp/index
      2. stop all nodes
      3. on node 10.3.3.19 delete folders /tmp/data and /tmp/index
      4. upgrade all nodes on 2.0.1-150-rel

      result for node where data was removed:
      root@ubu-2502:/tmp# dpkg -i /tmp/couchbase-server-enterprise_x86_64_2.0.1-150-rel.deb
      (Reading database ... 68049 files and directories currently installed.)
      Preparing to replace couchbase-server 2.0.0 (using .../couchbase-server-enterprise_x86_64_2.0.1-150-rel.deb) ...

      • Failed to stop couchbase-server
        libssl0.9.8 is installed. Continue installing
        Minimum RAM required : 4 GB
        System RAM configured : 4060188 kB

      Minimum number of processors required : 4 cores
      Number of processors on the system : 4 cores
      Upgrading previous couchbase ... (2.0.0)
      Stopping previous couchbase ... (2.0.0)

      • Failed to stop couchbase-server
        Saving previous couchbase config.dat ...
        Cleaning symlinks ...
        Unpacking replacement couchbase-server ...
        Setting up couchbase-server (2.0.1) ...
        Upgrading couchbase-server ...
        /opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
        Automatic mode: running without interactive questions or confirmations.
        Analysing...
        Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat.debsave
        Target node: ns_1@10.3.3.19
        ERROR: dbdir is not a directory: /tmp/data
        dpkg: error processing couchbase-server (--install):
        subprocess installed post-installation script returned error exit status 1
        Processing triggers for ureadahead ...
        Errors were encountered while processing:
        couchbase-server

      observation:
      start server mannualy:
      root@ubu-2502:/tmp# /etc/init.d/couchbase-server start

      • Started couchbase-server

      installed version is 2.0.1-150-rel

      the same test on centos is fine

      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 -

        given the test description this is a scenario which is not a major issue and it does not have a side effect that causes data loss or any other issue.

        moving this to 2.1

        Show
        farshid Farshid Ghods (Inactive) added a comment - given the test description this is a scenario which is not a major issue and it does not have a side effect that causes data loss or any other issue. moving this to 2.1
        Hide
        bcui Bin Cui added a comment -

        Since data are lost, upgrade process won't be able to identify the old config.dat file which contains bucket information. So ns_server will treat this scenario as new setup though.

        Show
        bcui Bin Cui added a comment - Since data are lost, upgrade process won't be able to identify the old config.dat file which contains bucket information. So ns_server will treat this scenario as new setup though.

          People

          • Assignee:
            bcui Bin Cui
            Reporter:
            andreibaranouski Andrei Baranouski
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes