Couchbase Server

Upgrade docs for 2.0 don't seem accurate

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0
  • Fix Version/s: None
  • Component/s: documentation
  • Security Level: Public
  • Labels:
    None

Description

According to this page: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-getting-started-upgrade-individual.html

The upgrade process should be an rpm -U, but that doesn't work when going from 1.8->2.0:
rpm -U couchbase-server-community_x86_64_2.0.0-beta.rpm
Stopping couchbase-server ...
Stopping couchbase-serverNOTE: shutdown failed
{badrpc,nodedown}

Upgrading couchbase-server ...
/opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
Traceback (most recent call last):
File "/opt/couchbase/bin/install/cbupgrade", line 11, in ?
import sqlite3
ImportError: No module named sqlite3
Starting couchbase-server[ OK ]

You have successfully installed Couchbase Server.
Please browse to http://fcddeva01:8091/ to configure your server.
Please refer to http://couchbase.com for additional resources.

Please note that you have to update your firewall configuration to
allow connections to the following ports: 11211, 11210, 11209, 4369,
8091 and from 21100 to 21299.

By using this software you agree to the End User License Agreement.
See /opt/couchbase/LICENSE.txt.

Stopping couchbase-serverNOTE: shutdown failed
{badrpc,nodedown}
--------------------------------------

I was under the impression that we were not supporting an in-place upgrade from 1.8 to 2.0, this upgrade scenario needs to be addressed and called out specifically as it will be frequently referred to and used by our existing customers.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
MC Brown added a comment -
The upgrade notes and process were provided by the engineering team. If they don't work, this is not a docs bug, but a software bug.
Show
MC Brown added a comment - The upgrade notes and process were provided by the engineering team. If they don't work, this is not a docs bug, but a software bug.
Hide
Permalink
Perry Krug added a comment -
Agreed, it was my mistake for not realizing what to/from builds were supported.

Apparently it is only being supported from 1.8.1 to 2.0 GA, could you just add a note to the upgrade docs saying such?
Show
Perry Krug added a comment - Agreed, it was my mistake for not realizing what to/from builds were supported. Apparently it is only being supported from 1.8.1 to 2.0 GA, could you just add a note to the upgrade docs saying such?
Hide
Permalink
MC Brown added a comment -
Er, you mean like the one on the upgrade page specifically written for 1.8 to 2.0 upgrades?

http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-getting-started-upgrade-1-8-2-0.html

Show
MC Brown added a comment - Er, you mean like the one on the upgrade page specifically written for 1.8 to 2.0 upgrades? http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-getting-started-upgrade-1-8-2-0.html
Hide
Permalink
Perry Krug added a comment -
There is nothing in there that describes it as not supported with any pre-beta releases, which is what the customer tried to do.

Also, given that people are google searching our documentation, there's no guarantee that they find this page before they find the actual instructions...so I would advocate it to be in both.
Show
Perry Krug added a comment - There is nothing in there that describes it as not supported with any pre-beta releases, which is what the customer tried to do. Also, given that people are google searching our documentation, there's no guarantee that they find this page before they find the actual instructions...so I would advocate it to be in both.
Hide
Permalink
MC Brown added a comment -
Your original request was not about about 'pre-beta releases', it was about version 1.8. The note about upgrades from pre-beta releases will be in the release notes, as it has been for all our pre-beta and beta release notes.

I'll add a link to the general upgrade section to the 1.8 to 2.0 specific section.
Show
MC Brown added a comment - Your original request was not about about 'pre-beta releases', it was about version 1.8. The note about upgrades from pre-beta releases will be in the release notes, as it has been for all our pre-beta and beta release notes. I'll add a link to the general upgrade section to the 1.8 to 2.0 specific section.
Hide
Permalink
Perry Krug added a comment -
No, the comment is about going from 1.8 TO pre-GA releases...which does not work and is not supported. That's what I want called out.
Show
Perry Krug added a comment - No, the comment is about going from 1.8 TO pre-GA releases...which does not work and is not supported. That's what I want called out.
Hide
Permalink
MC Brown added a comment -
That information is where it should be, in the release notes.
Show
MC Brown added a comment - That information is where it should be, in the release notes.
Hide
Permalink
MC Brown added a comment -
Documentation has been updated.
Show
MC Brown added a comment - Documentation has been updated.
Hide
Permalink
Perry Krug added a comment -
MC, I don't understand why this is so hard. People are not getting the information from the release notes, they are making mistakes, I'm asking you to help prevent that.
Show
Perry Krug added a comment - MC, I don't understand why this is so hard. People are not getting the information from the release notes, they are making mistakes, I'm asking you to help prevent that.
Hide
Permalink
MC Brown added a comment -
First of all, the documentation very clearly states, in each of the upgrade sections, that upgrades are only supported between 1.8 and 2.0. It does not say 2.0 beta, 2.0 pre-release, or any other combination other than 2.0.

Second, in the recent fix I committed, but which has been built yet, I have added a note about the incompatibility with beta and pre-release versions.
Show
MC Brown added a comment - First of all, the documentation very clearly states, in each of the upgrade sections, that upgrades are only supported between 1.8 and 2.0. It does not say 2.0 beta, 2.0 pre-release, or any other combination other than 2.0. Second, in the recent fix I committed, but which has been built yet, I have added a note about the incompatibility with beta and pre-release versions.

People

  • Assignee:
    MC Brown
    Reporter:
    Perry Krug
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: