Bug 1323075 - Volume status command failed during update from 3.1.2 to latest one, on non update node
Summary: Volume status command failed during update from 3.1.2 to latest one, on non ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Atin Mukherjee
QA Contact: Byreddy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-01 08:10 UTC by Byreddy
Modified: 2016-09-17 16:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-01 09:08:19 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Byreddy 2016-04-01 08:10:05 UTC
Description of problem:
=======================
Volume status command  failed on not updated node with error message "Commit failed on <host name of updated node>


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-1.el7


How reproducible:
==================
One time


Steps to Reproduce:
===================
1.Have two node cluster with rhgs 3.1.2 (node-1 and node-2)
2.Create and start  2*2 volume and do FUSE mount and start IO.
3.Update one of the node (say node-1) to latest 3.1.3 //follow in-service update procedure
4.Check volume status on node-2 multiple times

Actual results:
===============
Volume status on node-2 failed one time with error message "Commit failed on <host name of node-1>.


Expected results:
=================
Volume status command should not fail.


Additional info:
==================

Useful log info can be found below to debug

Comment 3 Atin Mukherjee 2016-04-01 09:08:19 UTC
First of all you'd need to provide log for dhcp37-171.lab.eng.blr.redhat.com to understand why the commit failed and more over this is not a supported configuration where all the nodes are not upgraded as we don't support hybrid cluster.

If required you can test this upstream and if you see the same issue file a bug upstream since we support heterogeneous cluster there, but in downstream this is not valid.


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