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

Bug 1491294

Summary:	op_version cannot be set to 31201
Product:	[Community] GlusterFS	Reporter:	Tony Becker <tbecker>
Component:	cli	Assignee:	Kaushal <kaushal>
Status:	CLOSED NOTABUG	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.12	CC:	amukherj, bugs, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-18 04:38:30 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 Tony Becker 2017-09-13 13:02:46 UTC

Description of problem:
op_version cannot be set to 31201

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

How reproducible:
Upgrade all cluster members to 3.12.1 and attempt to set new op-version with "gluster volume set all cluster.op-version 31201"

Actual results:
volume set: failed: Required op_version (31201) is not supported

Expected results:
success

Additional info:
Not sure if it's necessary to set new op_version here, was just doing it as standard procedure. I am using packaged version 3.12.1-ubuntu1~xenial1 from launchpad

Comment 2 Atin Mukherjee 2017-09-18 04:38:30 UTC

In 3.12.1 we haven't bumped up the op-version as there was no new option introduced which needs a new op-version all together, so you'd need to stick to 31200. Please note, it's not mandatory to bump up the op-version with every updates. Please use "gluster v get all cluster.max-op-version" to understand what's the op-version you'd need to bump to.