Bug 1569457

Summary: EIO errors on some operations when volume has mixed brick versions on a disperse volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Xavi Hernandez <jahernan>
Component: disperseAssignee: Xavi Hernandez <jahernan>
Status: CLOSED ERRATA QA Contact: Upasana <ubansal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: aspandey, bugs, jahernan, rhinduja, rhs-bugs, sankarshan, sheggodu, storage-qa-internal
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.12.2-13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1566732 Environment:
Last Closed: 2018-09-04 06:46:03 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:
Bug Depends On: 1566732    
Bug Blocks: 1503137    

Description Xavi Hernandez 2018-04-19 10:03:43 UTC
+++ This bug was initially created as a clone of Bug #1566732 +++

Description of problem:

If a disperse volume has different brick versions, some operations done on the volume will generate EIO errors.

Version-Release number of selected component (if applicable): mainline


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 Nag Pavan Chilakam 2018-05-16 12:45:33 UTC
Xavi,
can you help me with validation procedure.
1)What fops exactly were failing before fix
2)also when you are telling different brick version, are you refering to trusted.ec.version or the glusterfs version?

Comment 24 errata-xmlrpc 2018-09-04 06:46:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2607