[Bugs] [Bug 1223215] New: gluster volume status fails with locking failed error message

bugzilla at redhat.com bugzilla at redhat.com
Wed May 20 06:35:48 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1223215

            Bug ID: 1223215
           Summary: gluster volume status fails with locking failed error
                    message
           Product: GlusterFS
           Version: 3.7.0
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com
        Depends On: 1223213



+++ 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:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1223213
[Bug 1223213] gluster volume status fails with locking failed error message
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list