[Gluster-users] update from gluster 3.6.3 dependency problem

Niels de Vos
Thu, 14 Jan 2016 12:13:10 -0000

On Thu, Jan 14, 2016 at 09:52:43AM +0000, Kingsley
wrote:
> Hi,
>
> We're running gluster 3.6.3 on CentOS 7. A few weeks ago, the server
> started sending me messages like this:
>
> --8<--
> /etc/cron.daily/0yum-daily.cron:
>
> Failed to check for updates with the following error message:
> Failed to build transaction: glusterfs-server-3.6.3-1.el7.x86_64 requires
glusterfs-fuse = 3.6.3-1.el7
> glusterfs-server-3.6.3-1.el7.x86_64 requires glusterfs-libs = 3.6.3-1.el7
> glusterfs-server-3.6.3-1.el7.x86_64 requires glusterfs-cli = 3.6.3-1.el7
> glusterfs-server-3.6.3-1.el7.x86_64 requires glusterfs = 3.6.3-1.el7
> --8<--
>
> I thought that if I left it, the problem would be resolved, but it's
> still there. Is there a problem with the repo files?
>
> We've deliberately left the gluster repo disabled by default so that we
> can easily update the rest of the system without upsetting gluster, but
> it seems that 3.7.x has now been pushed into the CentOS repo.

Yes, RHEL updated the Gluster packages to 3.7.x. What you see here might
be from an attempt to update the glusterfs-fuse package from the CentOS
base/updates channel.

I think you run into this because you disabled the repository with the
glusterfs-server package in it. Could you check if enabling the
repository with the 3.6.x glusterfs-server package prevents this error?
yum should be smart enough to not update the glusterfs packages if it
sees that the most recent version of glusterfs-server is already
installed.

Thanks,
Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160114/a51452c1/attachment.sig>