Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1092592

Summary:	[RFE] We need a command to bump-up the glusterd op-version.
Product:	[Community] GlusterFS	Reporter:	Kaushal <kaushal>
Component:	glusterd	Assignee:	Kaushal <kaushal>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	mainline	CC:	amukherj, bugs, gluster-bugs, nsathyan, ravishankar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1091986	Environment:
Last Closed:	2014-11-11 08:31:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1091986, 1102055

Description Kaushal 2014-04-29 14:13:45 UTC

+++ This bug was initially created as a clone of Bug #1091986 +++

Description of problem:
Both  the snapshot feature and persistent AFR  xattrs implementation will work
only if op-version >=4.  To that effect we would need a gluster CLI
command to bump up the glusterd op-version when an existing cluster is
upgraded to the release containing these features.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Form a cluster and create a volume with a glusterfs release having cluster op-version less than 4.
2. Upgrade all nodes to the release having snapshot/ persistent AFR xattrs features.
3. Try snapshot/ add-brick/ remove-brick operations

Actual results:
Add/remove brick operations fail with the message:
One or more nodes do not support the required op-version. Cluster op-version must atleast be 4.

Similarly snapshots would also fail with an appropriate message (not checked the exact message yet).

Expected results:
These features should work.

Comment 1 Anand Avati 2014-04-29 14:15:40 UTC

REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#1) for review on master by Kaushal M (kaushal)

Comment 2 Anand Avati 2014-04-30 10:22:54 UTC

REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#2) for review on master by Kaushal M (kaushal)

Comment 3 Anand Avati 2014-04-30 17:25:45 UTC

REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#3) for review on master by Kaushal M (kaushal)

Comment 4 Anand Avati 2014-05-02 06:17:06 UTC

REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#4) for review on master by Kaushal M (kaushal)

Comment 5 Anand Avati 2014-05-02 10:31:48 UTC

REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#5) for review on master by Kaushal M (kaushal)

Comment 6 Anand Avati 2014-05-06 09:41:00 UTC

COMMIT: http://review.gluster.org/7603 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit fb173e9a10d62d49cc8b57c6b3c5bbdf1b326c18
Author: Kaushal M <kaushal>
Date:   Tue Apr 29 19:12:20 2014 +0530

    glusterd: Allow bumping up the cluster op-version
    
    This patch allows a user to bump up the cluster op-version by doing
      # gluster volume set all cluster.op-version <OP-VERSION>
    
    The op-version will be bumped only if
    - all the peers in the cluster support it, and
    - the new op-version is greater than the current cluster op-version
    
    This set operation will not do any other change other than changing and
    saving the cluster op-version in the glusterd.info file. It will NOT,
    - change any existing volume
    - add the option to the global options list
    - fix the cluster op-version to the given version, it can be bumped up
      by other volume set commands.
    
    Change-Id: I084b4fcc45e79dc2ca7b7680d7bb371bb175af39
    BUG: 1092592
    Signed-off-by: Kaushal M <kaushal>
    Reviewed-on: http://review.gluster.org/7603
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 7 Niels de Vos 2014-09-22 12:39:22 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 8 Niels de Vos 2014-11-11 08:31:27 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users