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@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users