Bug 1454558 - qemu_gluster_co_get_block_status gets SIGABRT when doing blockcommit continually
Summary: qemu_gluster_co_get_block_status gets SIGABRT when doing blockcommit continually
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: protocol
Version: rhgs-3.2
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.3.0
Assignee: Ravishankar N
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1417151 1425293
TreeView+ depends on / blocked
 
Reported: 2017-05-23 04:13 UTC by Atin Mukherjee
Modified: 2017-09-21 04:58 UTC (History)
18 users (show)

Fixed In Version: glusterfs-3.8.4-26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1425293
Environment:
Last Closed: 2017-09-21 04:45:37 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Comment 3 Ravishankar N 2017-05-23 04:50:29 UTC 
Downstream patch on rhgs-3.3 branch: https://code.engineering.redhat.com/gerrit/#/c/106934/
Comment 7 SATHEESARAN 2017-08-11 18:36:34 UTC 
Tested with glusterfs-3.8.4-39.el7rhgs

1. Converted QEMU image in to raw image worked good
# qemu-img convert -f qcow2 -O raw gluster://<server>/<vol>/vm1.img gluster://<server>/<vol>/vm1.raw

2. I have created couple of snapshots of the VM and did a repeated blockcommit & blockjob too. All worked good.

Based on the above observation, marking this bug as VERIFIED
Comment 9 errata-xmlrpc 2017-09-21 04:45:37 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/RHBA-2017:2774
Comment 10 errata-xmlrpc 2017-09-21 04:58:49 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/RHBA-2017:2774
Note You need to log in before you can comment on or make changes to this bug.