[Gluster-users] Gluster Update
Joe Julian
joe at julianfamily.org
Mon Jun 9 12:18:14 UTC 2014
RHS is downstream. Note the "rhs" in the rpm version that was conflicting from base/upgrade.
download.gluster.org is our upstream repo.
On June 9, 2014 4:53:06 AM PDT, "Kurian @ GnuHack" <kurian at gnuhack.com> wrote:
>Thank you Joe.
>
>OK. We haven't enabled RHS repo and the gluster 3.4 is included in
>system-updates / system-base repos. So that makes it upstream version
>right? Hence is it okay to upgrade to 3.4?
>
>Regards,
>Kurian.
>
>
>
>
>On Monday 09 June 2014 05:04 PM, Joe Julian wrote:
>> Oh, and yes. 3.4 is the recommended stable version, though the
>> developers seem to like to recommend 3.5.
>>
>> On 6/9/2014 4:18 AM, Kurian @ GnuHack wrote:
>>> Thank you Julian..
>>>
>>> So I will do the minor update of 3.3 for now and then will remove
>the
>>> exclusion from base / updates repo and proceed to 3.4.
>>>
>>> 3.3 -> 3.4 update is supported and stable?
>>>
>>> Regards,
>>> Kurian.
>>> On Monday 09 June 2014 04:35 PM, Joe Julian wrote:
>>>> Add:
>>>>
>>>> exclude=gluster*
>>>>
>>>> to base and updates.
>>>>
>>>> On June 9, 2014 3:23:17 AM PDT, "Kurian @ GnuHack"
>>>> <kurian at gnuhack.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> We have been using gluster in our 2 node webserver. Where
>>>> glusterd and gluster-client both on the same servers. This is
>>>> configured in Replicate mode. OS is centos 6. Gluster was
>>>> installed using glusterfs-epel repo which was version was at
>>>> that time version 3.3.
>>>>
>>>> There were few minor updates which we missed to perform on the
>>>> servers. Now when I do yum update, I get dependency conflict as
>>>> new version of gluster 3.4 is available in system-updates /
>>>> system-base repo.
>>>>
>>>> To resolve this, should I disable system-update / system-base
>>>> repo, proceed with minor update 3.3 first and then enable
>>>> system-updates / system-base repo back and upgrade to 3.4?
>>>>
>>>> Or should I disable gluster-repo permanently and upgrade to 3.4
>>>> directly?
>>>>
>>>> How will I proceed further now.
>>>>
>>>> *Error: Package: glusterfs-server-3.3.1-15.el6.x86_64
>>>> (glusterfs-epel)**
>>>> ** Requires: glusterfs-fuse = 3.3.1-15.el6**
>>>> ** Removing: glusterfs-fuse-3.3.1-1.el6.x86_64
>>>> (@glusterfs-epel)**
>>>> ** glusterfs-fuse = 3.3.1-1.el6**
>>>> ** Updated By:
>>>> glusterfs-fuse-3.4.0.57rhs-1.el6_5.x86_64 (system-updates)**
>>>> ** glusterfs-fuse = 3.4.0.57rhs-1.el6_5**
>>>> ** Available: glusterfs-fuse-3.3.1-15.el6.x86_64
>>>> (glusterfs-epel)**
>>>> ** glusterfs-fuse = 3.3.1-15.el6**
>>>> ** Available: glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64
>>>> (system-base)**
>>>> ** glusterfs-fuse = 3.4.0.36rhs-1.el6**
>>>> **Error: Package: glusterfs-server-3.3.1-15.el6.x86_64
>>>> (glusterfs-epel)**
>>>> ** Requires: glusterfs = 3.3.1-15.el6**
>>>> ** Removing: glusterfs-3.3.1-1.el6.x86_64
>>>> (@glusterfs-epel)**
>>>> ** glusterfs = 3.3.1-1.el6**
>>>> ** Updated By: glusterfs-3.4.0.57rhs-1.el6_5.x86_64
>>>> (system-updates)**
>>>> ** glusterfs = 3.4.0.57rhs-1.el6_5**
>>>> ** Available: glusterfs-3.3.1-15.el6.x86_64
>>>> (glusterfs-epel)**
>>>> ** glusterfs = 3.3.1-15.el6**
>>>> ** Available: glusterfs-3.4.0.36rhs-1.el6.x86_64
>>>> (system-base)**
>>>> ** glusterfs = 3.4.0.36rhs-1.el6**
>>>> *
>>>> I should have done the update in a regular basis. Now I need
>>>> your suggestions to resolve this mess.
>>>>
>>>> Regards,
>>>> Kurian.
>>>>
>>>>
>------------------------------------------------------------------------
>>>>
>>>> Gluster-users mailing list
>>>> Gluster-users at gluster.org
>>>> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>>>>
>>>>
>>>> --
>>>> Sent from my Android device with K-9 Mail. Please excuse my
>brevity.
>>>
>>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140609/2ebb0d03/attachment.html>
More information about the Gluster-users
mailing list