Bug 1155518 – qemu-kvm: undefined symbol: glfs_discard_async

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1155518 - qemu-kvm: undefined symbol: glfs_discard_async

Summary:	qemu-kvm: undefined symbol: glfs_discard_async

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	qemu-kvm (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Miroslav Rezanina
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1157329
	Show dependency tree / graph

Reported:	2014-10-22 05:28 EDT by Xu Han
Modified:	2015-03-05 03:12 EST (History)
CC List:	12 users (show)

See Also:
Fixed In Version:	qemu-kvm-1.5.3-78.el7
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Clones:	1157329 (view as bug list)
Environment:
Last Closed:	2015-03-05 03:12:51 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:0349	normal	SHIPPED_LIVE	Important: qemu-kvm security, bug fix, and enhancement update	2015-03-05 07:27:34 EST

Groups: None (edit)

Description Xu Han 2014-10-22 05:28:13 EDT

Description of problem:
Because of the old glusterfs api, QEMU will quit with error message:
    symbol lookup error: /usr/libexec/qemu-kvm: undefined symbol: glfs_discard_async

so need to specify the requirement of 'glusterfs-api'.

I just tested following packages:
glusterfs-api-3.4.0.59rhs-1.el7.x86_64    FAILED
glusterfs-api-3.6.0.29-2.el7.x86_64       PASSED


Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-76.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. launch QEMU
# /usr/libexec/qemu-kvm

Actual results:
# /usr/libexec/qemu-kvm
/usr/libexec/qemu-kvm: symbol lookup error: /usr/libexec/qemu-kvm: undefined symbol: glfs_discard_async

Expected results:
no quits

Additional info:

Comment 2 Alex Jia 2014-11-07 03:53:25 EST

You need to update glusterfs-libs, and then it should work well. the gluster doesn't have API symbol versioning, please refer to bug 1096654.

Comment 4 Miroslav Rezanina 2014-11-10 04:29:59 EST

Fix included in qemu-kvm-1.5.3-78.el7

Comment 6 mazhang 2014-11-12 06:42:08 EST

Reproduce this bug with qemu-kvm-1.5.3-75.el7.

Steps:
# rpm -qa |grep gluster
glusterfs-3.4.0.70rhs-1.el7.x86_64
glusterfs-api-3.4.0.70rhs-1.el7.x86_64
glusterfs-libs-3.4.0.70rhs-1.el7.x86_64
# rpm -ivh qemu-kvm-1.5.3-75.el7.x86_64.rpm qemu-img-1.5.3-75.el7.x86_64.rpm qemu-kvm-common-1.5.3-75.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:qemu-kvm-common-10:1.5.3-75.el7  ################################# [ 33%]
   2:qemu-img-10:1.5.3-75.el7         ################################# [ 67%]
   3:qemu-kvm-10:1.5.3-75.el7         ################################# [100%]

qemu-kvm install complete without error.


Verify this bug on qemu-kvm-1.5.3-79.el7.x86_64
# rpm -qa |grep gluster
glusterfs-3.4.0.70rhs-1.el7.x86_64
glusterfs-api-3.4.0.70rhs-1.el7.x86_64
glusterfs-libs-3.4.0.70rhs-1.el7.x86_64
# rpm -ivh qemu-img-1.5.3-79.el7.x86_64.rpm qemu-kvm-1.5.3-79.el7.x86_64.rpm qemu-kvm-common-1.5.3-79.el7.x86_64.rpm 
error: Failed dependencies:
	glusterfs-api >= 3.6.0 is needed by qemu-kvm-10:1.5.3-79.el7.x86_64

Can not install qemu-kvm with glusterfs-api-3.4.0.70rhs-1.el7.x86_64, must upgrade glusterfs-api>=3.6.0.
After upgrade to glusterfs-api-3.6.0.29-2.el7.x86_64, install successful.

So this bug has been fixed.

Comment 9 errata-xmlrpc 2015-03-05 03:12:51 EST

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://rhn.redhat.com/errata/RHSA-2015-0349.html

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