Bug 1168897
Summary: | Attempt remove-brick after node has terminated in cluster gives error: volume remove-brick commit force: failed: One or more nodes do not support the required op-version. Cluster op-version must atleast be 30600. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | john.lane |
Component: | build | Assignee: | bugs <bugs> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.1 | CC: | bugs, jdarcy, john.lane, kaushal, khoi.mai2008, mailbox, matorola |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-30 12:47:25 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
john.lane
2014-11-28 11:03:00 UTC
Have found can 'fix' the issue by changing the glusterd.info setting for the op-version:
diff glusterd.info glusterd.info.orig
2c2
< operating-version=30600
---
> operating-version=30501
and restarting glusterd.
Presumably, the glusterfs-server package update forgets to modify this file.
Probably should be operating-version=30601 But above works. is there a cLi command that would update that file in 3.5.3? When I try to execute what I searched: https://botbot.me/freenode/gluster/search/?q=op-version # gluster volume set all cluster.op-version 30501 volume set: failed: option : cluster.op-version does not exist Did you mean cluster.eager-lock? am I doing something wrong? Can someone bump version for this bug to mainline, since it is still present in 3.6.2 (package glusterfs-3.6.2-1.fc21.x86_64) ? Thanks. [root@node01 ~]# rpm -q glusterfs glusterfs-3.6.2-1.fc21.x86_64 [root@node01 ~]# gluster vol info vol1 Volume Name: vol1 Type: Replicate Volume ID: 5b6ae6c7-6139-45b5-b4af-d2f21709f6f2 Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node01:/export/sdb1/brick Brick2: node02:/export/sdb1/brick [root@node01 ~]# gluster vol remove-brick vol1 replica 1 node02:/export/sdb1/brick force Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y volume remove-brick commit force: failed: One or more nodes do not support the required op-version. Cluster op-version must atleast be 30600. Seen also while using 3.6.2 from Ubuntu PPA (http://ppa.launchpad.net/gluster/glusterfs-3.6/ubuntu) on Ubuntu 14.04. My /var/lib/glusterd.info contains a `operating-version=2` line; when changed to `operating-version=30601` prevented the daemon to start, leaving the following in the logs: E [glusterd-store.c:2037:glusterd_restore_op_version] 0-management: wrong op-version (30601) retrieved E [glusterd-store.c:4278:glusterd_restore] 0-management: Failed to restore op_version E [xlator.c:425:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again GlusterFS doesn't automatically update the op-version. This is done to prevent incompatibilities when doing a rolling update of a GlusterFS cluster. Users need to bump the op-version after all servers in the cluster have been upgraded. From GlusterFS-3.6, the command `gluster volume set all cluster.op-version <version>` can be used to set the op-version. More information regarding this can be obtained from https://gluster.readthedocs.io/en/latest/Upgrade-Guide/op_version/ |