Bug 1454558
| Summary: | qemu_gluster_co_get_block_status gets SIGABRT when doing blockcommit continually | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Atin Mukherjee <amukherj> |
| Component: | protocol | Assignee: | Ravishankar N <ravishankar> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.2 | CC: | amukherj, chhu, crobinso, dyuan, hhan, jcody, juzhang, knoel, mzywusko, ndevos, rcyriac, rhinduja, rhs-bugs, rkavunga, storage-qa-internal, virt-maint, xuzhang, yanqzhan |
| Target Milestone: | --- | Keywords: | Regression, TestBlocker |
| Target Release: | RHGS 3.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.8.4-26 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1425293 | Environment: | |
| Last Closed: | 2017-09-21 04:45:37 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: | |||
| Bug Blocks: | 1417151, 1425293 | ||
|
Comment 3
Ravishankar N
2017-05-23 04:50:29 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 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 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 |