[Gluster-devel] glusterfs 3.4.0 vs 3.4.1 potential packaging problem?

[Jeff Vance]

Hello Niels,

I was not clear enough in my description. Here's what I did:

1) several weeks ago, installed f19 from an ISO in a VM
2) several weeks ago, yum install glusterfs glusterfs-server glusterfs-fuse  # note: no glusterfs-libs
3) ^^ pulled in glusterfs 3.4.0 at the time
4) yesterday, did the same yum install, again w/o glusterfs-libs  # did not bring in glusterfs-libs
5) see the condition I originally described.

Jeff

----- Original Message -----
From: "Niels de Vos" <ndevos at redhat.com>
To: "Anand Avati" <avati at gluster.org>
Cc: "Jeff Vance" <jvance at redhat.com>, "Gluster Devel" <gluster-devel at nongnu.org>
Sent: Wednesday, October 9, 2013 1:47:52 AM
Subject: Re: [Gluster-devel] glusterfs 3.4.0 vs 3.4.1 potential packaging problem?

On Tue, Oct 08, 2013 at 02:26:50PM -0700, Anand Avati wrote:
> >
> > [2013-10-08 17:33:36.662549] I [glusterfsd.c:1910:main]
> > 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.4.1
> > (/usr/sbin/glusterd --debug)
> >
> 
> ...
> 
> 
> > [2013-10-08 17:33:36.664191] W [xlator.c:185:xlator_dynload] 0-xlator:
> > /usr/lib64/glusterfs/3.4.0/xlator/mgmt/glusterd.so: cannot open shared
> > object file: No such file or directory
> 
> 
> 
> I think the issue can be summarized with the above two log lines. glusterd
> binary is version 3.4.1 (PACKAGE_VERSION of glusterfsd is "3.4.1") but
> libglusterfs is trying to open ".../3.4.0/...glusterd.so" (i.e
> PACKAGE_VERSION during build of libglusterfs.so is "3.4.0").
> 
> The reality in code today is that glusterfsd and libglusterfs must be built
> from the same version of the source tree (for reasons like above), and this
> needs to be captured in the packaging.
> 
> I see that the glusterfs.spec.in in glusterfs.git has:
> 
> Requires:         %{name}-libs = %{version}-%{release}
> 
> for the glusterfs-server RPM. That should have forced your glusterfs-libs
> to be updated to 3.4.1 as well.
> 
> Kaleb,
> Can you confirm that the Fedora RPMs also have this "internal dependency"
> between packages? If it already does, I'm not sure how Jeff ended up with:
> 
> glusterfs-libs-3.4.0-8.fc19.x86_64
> glusterfs-3.4.1-1.fc19.x86_64
> 
> without doing a --force and/or --nodeps install.

I installed a clean Fedora 19, installed glusterfs packages (without the 
available updates) and updated the system with 'yum update'. For me this 
pulled the correct glusterfs-libs. I am not sure how getting mixed 
versions is possible without looking at the /var/log/yum.log.

    # rpm -qa 'glusterfs*'
    glusterfs-libs-3.4.1-1.fc19.i686
    glusterfs-server-3.4.1-1.fc19.i686
    glusterfs-3.4.1-1.fc19.i686
    glusterfs-cli-3.4.1-1.fc19.i686
    glusterfs-fuse-3.4.1-1.fc19.i686
    # rpm -q --requires glusterfs | grep glusterfs-libs
    glusterfs-libs = 3.4.1-1.fc19

Cheers,
Niels