Bug 1491294 - op_version cannot be set to 31201
Summary: op_version cannot be set to 31201
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.12
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kaushal
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-13 13:02 UTC by Tony Becker
Modified: 2017-09-18 04:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-18 04:38:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.