https://bugzilla.redhat.com/show_bug.cgi?id=1224891
Bug ID: 1224891
Summary: gluster volume status fails with locking failed error
message
Product: Red Hat Gluster Storage
Version: 3.1
Component: glusterfs-server
Severity: medium
Assignee: rhs-bugs at redhat.com
Reporter: amukherj at redhat.com
QA Contact: storage-qa-internal at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
nlevinki at redhat.com, sasundar at redhat.com,
vbellur at redhat.com
Depends On: 1223213
Blocks: 1223215
+++ This bug was initially created as a clone of Bug #1223213 +++
Description of problem:
When a node in a multi node cluster is upgraded from 3.5 to 3.7 gluster volume
status fails with locking failed error message
Version-Release number of selected component (if applicable):
Mainline
How reproducible:
Always
Steps to Reproduce:
1. Create a multi node cluster running with 3.5 version
2. Upgrade any node to 3.7
3. Execute gluster volume status
Actual results:
gluster volume status fails with locking failed error message
Expected results:
gluster volume status should be successful
Additional info:
--- Additional comment from Anand Avati on 2015-05-20 09:02:36 EDT ---
REVIEW: http://review.gluster.org/10842 (glusterd : allocate peerid to store in
frame->cookie) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Anand Avati on 2015-05-22 01:01:01 EDT ---
REVIEW: http://review.gluster.org/10842 (glusterd : allocate peerid to store in
frame->cookie) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1223213
[Bug 1223213] gluster volume status fails with locking failed error message
https://bugzilla.redhat.com/show_bug.cgi?id=1223215
[Bug 1223215] gluster volume status fails with locking failed error message
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=8u8v55DHQX&a=cc_unsubscribe