Re: [Users] Trouble upgrading

On 11/22/2013 06:25 AM, Bob Doolittle wrote: > > On 11/21/2013 07:53 PM, Itamar Heim wrote: >> On 11/22/2013 02:52 AM, Bob Doolittle wrote: >>> >>> On 11/21/2013 07:48 PM, Itamar Heim wrote: >>>> On 11/22/2013 02:33 AM, Bob Doolittle wrote: >>>>> >>>>> On 11/21/2013 12:57 PM, Itamar Heim wrote: >>>>>> On 11/21/2013 07:38 PM, Bob Doolittle wrote: >>>>>>> >>>>>>> On 11/21/2013 12:00 PM, Itamar Heim wrote: >>>>>>>> On 11/21/2013 06:32 PM, Bob Doolittle wrote: >>>>>>>>> Yay! >>>>>>>>> >>>>>>>>> Congratulations to all of the oVirt team. >>>>>>>>> >>>>>>>>> I am having trouble locating upgrade instructions, however. >>>>>>>>> There's >>>>>>>>> nothing in the release notes. >>>>>>>>> >>>>>>>>> I discovered through trial-and-error that running "engine-setup" >>>>>>>>> again >>>>>>>>> handles upgrade of the Engine. >>>>>>>>> >>>>>>>>> But I don't know how to upgrade my RH 6.4 KVM host. When I try to >>>>>>>>> run >>>>>>>>> "yum update" it fails due to dependency errors notably in: >>>>>>>>> glusterfs >>>>>>>>> qemu >>>>>>>>> vdsm >>>>>>>>> >>>>>>>> >>>>>>>> can you please include the yum output log? >>>>>>> >>>>>>> Sorry yes. Attached are three outputs. First my repolist. Then yum >>>>>>> update with no options, and yum update with --skip-broken (so you >>>>>>> can >>>>>>> see the lurking issues masked by the first failure). >>>>>>> >>>>>>> It appears that the glusterfs issue is due to a newer version >>>>>>> offered by >>>>>>> rhel-x86_64-server-6: glusterfs-3.4.0.36rhs-1.el6.x86_64. This has >>>>>>> dependencies which conflict with the version provided by >>>>>>> ovirt-stable >>>>>>> (and glusterfs-epel). >>>>>>> >>>>>>> It looks like there was a large update to the Red Hat repo last >>>>>>> night >>>>>>> that has caused conflicts with ovirt-stable. >>>>>>> >>>>>>> Note I can get it to the point where it's willing to install >>>>>>> packages if >>>>>>> I specify --skip-broken and also --exclude vdsm-python-4.12.1, but >>>>>>> that's a bit too scary for me without checking first. >>>>>> >>>>>> oh, you may caught rhel repo in middle of a refresh - try again in a >>>>>> few hours first, but could be the refresh may cause an issue we'd >>>>>> need >>>>>> to resolve. >>>>> >>>>> Not sure why I'm the only person reporting this (am I the only person >>>>> who runs RH 6 on their KVM hosts who has tried upgrading??), but the >>>>> problem has not resolved. >>>>> >>>>> What's the next step? Does it need a bug opened? >>>>> >>>>> Let me know if I can provide any more information. >>>>> >>>> >>>> have you tried refreshing your repo / clear yum cache? >>>> (since glusterfs-3.4.0.36rhs-1.el6 should be in the repo) >>> >>> I just did "yum clean all; yum update". Same result. >>> >> >> do you have glusterfs-3.4.0.36rhs-1.el6 in the repo? > > Apparently: > >> Error: Package: glusterfs-cli-3.4.0-8.el6.x86_64 (@glusterfs-epel) >> Requires: glusterfs-libs = 3.4.0-8.el6 >> Removing: glusterfs-3.4.0-8.el6.x86_64 (@glusterfs-epel) >> glusterfs-libs = 3.4.0-8.el6 >> Updated By: glusterfs-3.4.0.36rhs-1.el6.x86_64 >> (rhel-x86_64-server-6) >> Not found >> Removing: glusterfs-libs-3.4.0-8.el6.x86_64 (@glusterfs-epel) >> glusterfs-libs = 3.4.0-8.el6 >> Updated By: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 >> (rhel-x86_64-server-6) >> glusterfs-libs = 3.4.0.36rhs-1.el6 >> Available: glusterfs-3.2.7-1.el6.i686 (epel) >> glusterfs-libs = 3.2.7-1.el6 > > If you are using EPEL packages to create/run gluster volumes on RHEL (essentially the server side functionality of gluster), it would be better to move to GlusterFS 3.4.1 and then try the upgrade. If you are not making use of gluster's server side packages, you can remove glusterfs-cli and related dependencies. If an upgrade is initiated after that, it should go through. Regards, Vijay