Description: ------------- Currently when we install qemu-kvm, it pulls glusterfs-api as dependency, which in turn pulls glusterfs-libs. But for making use of QEMU Driver for glusterfs, 'glusterfs' package is also required. But after installing, 'glusterfs-api' I see that, 'glusterfs' was not pulled in as a dependency. So QEMU should be dependent on 'glusterfs' package and not 'glusterfs-api' package. Steps : -------- 1. Install QEMU ( latest version which has got QEMU driver for glusterfs ) 2. Check glusterfs, glusterfs-api, gluster-libs are installed as dependency Actual Result: -------------- only glusterfs-libs and glusterfs-api packages are installed 'glusterfs' package is missed in the dependency Expected Result: --------------- 'glusterfs' package should be pulled in as dependency
(In reply to SATHEESARAN from comment #1) > Description: > ------------- > Currently when we install qemu-kvm, it pulls glusterfs-api as dependency, > which in turn pulls glusterfs-libs. But for making use of QEMU Driver for > glusterfs, 'glusterfs' package is also required. > > But after installing, 'glusterfs-api' I see that, 'glusterfs' was not pulled > in as a dependency. So QEMU should be dependent on 'glusterfs' package and > not 'glusterfs-api' package. > > Steps : > -------- > 1. Install QEMU ( latest version which has got QEMU driver for glusterfs ) Typo here - Install 'qemu-kvm' (i.e) yum install qemu-kvm > 2. Check glusterfs, glusterfs-api, gluster-libs are installed as dependency > > Actual Result: > -------------- > only glusterfs-libs and glusterfs-api packages are installed > 'glusterfs' package is missed in the dependency > > Expected Result: > --------------- > 'glusterfs' package should be pulled in as dependency
Just checked the master branch: $ ./autogen.sh && ./configure && make -C extras/LinuxRPM testsrpm $ rpmbuild --define "_topdir $PWD' --rebuild glusterfs-3.7dev-*.src.rpm $ rpm -q --requires -p RPMS/x86_64/glusterfs-api-3.7dev-*.x86_64.rpm | \ grep ^glusterfs glusterfs = 3.7dev-0.125.git77ce886.fc20 So, in current mainline, glusterfs-api already depends on the glusterfs package. I also downloaded the nightly build for release-3.5, and here glusterfs-api also depends on glusterfs of the same version. Should this bug be filed against version 3.4 instead?
(In reply to Niels de Vos from comment #3) > Just checked the master branch: > > $ ./autogen.sh && ./configure && make -C extras/LinuxRPM testsrpm > $ rpmbuild --define "_topdir $PWD' --rebuild glusterfs-3.7dev-*.src.rpm > $ rpm -q --requires -p RPMS/x86_64/glusterfs-api-3.7dev-*.x86_64.rpm | \ > grep ^glusterfs > glusterfs = 3.7dev-0.125.git77ce886.fc20 > > So, in current mainline, glusterfs-api already depends on the glusterfs > package. > > I also downloaded the nightly build for release-3.5, and here glusterfs-api > also depends on glusterfs of the same version. > > Should this bug be filed against version 3.4 instead? OK. It is my fault, I haven't checked that. It should be in 3.4 then Changing the version to 3.4. Thanks Neils
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug.