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

Bug 1228785

Summary:	Cannot add brick without manually setting op-version
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	replicate	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs, joe, ravishankar, rkavunga, smohan
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 05:45:49 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:

Description Joe Julian 2015-06-05 17:43:02 UTC

Description of problem:
# gluster volume add-brick test replica 2 questor:/tmp/gluster/test/2
volume add-brick: failed: One or more nodes do not support the required op-version. Cluster op-version must atleast be 30600.

Version-Release number of selected component (if applicable):
glusterfs-3.6.3-1.fc21.x86_64

How reproducible:
Always

Steps to Reproduce:
1. gluster volume create test questor:/tmp/gluster/test/1
2. gluster volume start test
3. mount -t glusterfs localhost:test /mnt
4. gluster volume add-brick test replica 2 questor:/tmp/gluster/test/2

Actual results:
volume add-brick: failed: One or more nodes do not support the required op-version. Cluster op-version must atleast be 30600.

Expected results:
volume add-brick: success

Additional info:

Comment 1 Atin Mukherjee 2015-06-09 12:16:04 UTC

I believe this has happened because of an upgrade. Probably the cluster was earlier running with a version < 3.6 and the upgrade happened. Until and unless we manually bump up the op-version this is expected and not a bug. Could you re-confirm?

Comment 2 Mohammed Rafi KC 2015-06-30 12:26:45 UTC

Based on comment 1, closing this bug as "not a bug". Please feel free to reopen it, if you still able to reproduce it.

Comment 3 Joe Julian 2015-10-20 20:54:11 UTC

This is a bug according to the feature page:
http://www.gluster.org/community/documentation/index.php/Features/Opversion

When no features of a higher op-version are being used, the cluster should drop down to the lowest common op-version for the feature set that is implemented.

Adding a brick has been supported since glusterd first was implemented. The lowest op-version possible should be sufficient for that feature.

This is still a problem as of 3.7.4

Comment 4 Kaushal 2017-03-08 11:04:53 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

Comment 5 Atin Mukherjee 2017-03-08 17:49:17 UTC

I think this limitation was brought in due to some AFR changes. Ravi, can you please confirm?

Comment 6 Ravishankar N 2017-03-09 02:13:24 UTC

Yes I think it was introduced by https://review.gluster.org/#/c/7122/ for glusterfs-3.6. I don't think this issue would occur in any of the currently supported (i.e. non EOL'ed) versions of gluster.

Comment 7 Ravishankar N 2017-03-09 04:12:04 UTC

Joe/ Atin, can we close the bug if the issue does not occur in 3.8 or 3.10?

Comment 8 Atin Mukherjee 2017-03-09 04:40:37 UTC

I think we can, will leave it to Joe for his final call.

Comment 9 Ravishankar N 2018-11-20 05:45:49 UTC

Closing this bug based on comment#6. Please re-open if issue persists in a currently supported gluster version.