Re: [Users] Trouble Upgrading (Fedora)
Joining two threads on that subject On Sun, Nov 24, 2013 at 11:32:55AM -0500, Yaniv Bronheim wrote: > Hey, > > - Original Message - > > From: "Nicholas Kesick" > > To: "oVirt Mailing List" > > Sent: Friday, November 22, 2013 6:55:23 PM > > Subject: [Users] Trouble Upgrading (Fedora) > > > > I am having trouble upgrading on Fedora 19 to 3.3.1. > > > > Two observations: > > 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update. > > > > > > 2) There is a dependency update circle involving > > python-cpopen-1.2.3-4.fc19.x86_64 and dsm-python-cpopen.x86_64 > > 0:4.13.0-11.fc19 > > This issue is fine. Not so smoothly but we had to do that. > cpopen package is published as part of vdsm code in ovirt-3.3 and before, > On master branch we require python-cpopen formal package that is shipped with > fedora\rhel currently . > > Each time you'll switch between newer version of current master (3.4) to > ovirt-3.3 or older you will notice this report We should break this vicious cycle. I think it was intended to simplify "upgrade" from ovirt-3.4 to ovirt-3.3 on Jenkins slaves. But that's plain wrong on a wider context. The Jenkins issue should be solved explicitly by removing python-cpopen when vdsm-python-cpopen has to be installed. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
Il 28/11/2013 13:15, Dan Kenigsberg ha scritto: > On Thu, Nov 28, 2013 at 01:06:06AM -0500, Balamurugan Arumugam wrote: >> >>> On 11/21/2013 11:32 AM, Bob Doolittle wrote: 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 and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? >>> >>> Just to summarize: >>> >>> There is a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1033587) >>> which prevents updates of the Host/Node for users of the Red Hat 6 >>> official channels. A fix will be forthcoming. >>> >>> In the meantime, a workaround is to edit >>> /etc/yum.repos.d/glusterfs-epel.repo to globally change the version >>> string "3.4.0" to "LATEST". A new ovirt-release-9-1 rpm has been published in stable repo updating glusterfs release to LATEST. >>> >> >> I sent a fix [1] to vdsm to add glusterfs dependency conditionally. Please >> let me know if this helps. >> >> >> Regards, >> Bala >> >> [1] http://gerrit.ovirt.org/#/c/21705/ > > I think that this is unhelpful for two reasons: > 1. Bob complains about ovirt-3.3, and you patch master. > 2. We cannot take your patch to master since we already have code that >expects glusterfs>=3.4.1 (http://gerrit.ovirt.org/10200). > > I believe that taking http://gerrit.ovirt.org/#/c/21794/ into > ovirt-release would fix Bob's issues. > > Dan. > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On Thu, Nov 28, 2013 at 01:06:06AM -0500, Balamurugan Arumugam wrote: > > > On 11/21/2013 11:32 AM, Bob Doolittle wrote: > > > 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 > > > > > > and also to a multilib version error due to vdsm-python 4.12 and 4.13. > > > > > > What's the proper upgrade procedure for a Host? > > > > Just to summarize: > > > > There is a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1033587) > > which prevents updates of the Host/Node for users of the Red Hat 6 > > official channels. A fix will be forthcoming. > > > > In the meantime, a workaround is to edit > > /etc/yum.repos.d/glusterfs-epel.repo to globally change the version > > string "3.4.0" to "LATEST". > > > > I sent a fix [1] to vdsm to add glusterfs dependency conditionally. Please > let me know if this helps. > > > Regards, > Bala > > [1] http://gerrit.ovirt.org/#/c/21705/ I think that this is unhelpful for two reasons: 1. Bob complains about ovirt-3.3, and you patch master. 2. We cannot take your patch to master since we already have code that expects glusterfs>=3.4.1 (http://gerrit.ovirt.org/10200). I believe that taking http://gerrit.ovirt.org/#/c/21794/ into ovirt-release would fix Bob's issues. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
- Original Message - > From: "Bob Doolittle" > To: users@ovirt.org > Sent: Wednesday, November 27, 2013 12:05:20 AM > Subject: Re: [Users] Trouble upgrading > > On 11/21/2013 11:32 AM, Bob Doolittle wrote: > > 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 > > > > and also to a multilib version error due to vdsm-python 4.12 and 4.13. > > > > What's the proper upgrade procedure for a Host? > > Just to summarize: > > There is a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1033587) > which prevents updates of the Host/Node for users of the Red Hat 6 > official channels. A fix will be forthcoming. > > In the meantime, a workaround is to edit > /etc/yum.repos.d/glusterfs-epel.repo to globally change the version > string "3.4.0" to "LATEST". > I sent a fix [1] to vdsm to add glusterfs dependency conditionally. Please let me know if this helps. Regards, Bala [1] http://gerrit.ovirt.org/#/c/21705/ > Thanks, > Bob > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/21/2013 11:32 AM, Bob Doolittle wrote: 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 and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Just to summarize: There is a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1033587) which prevents updates of the Host/Node for users of the Red Hat 6 official channels. A fix will be forthcoming. In the meantime, a workaround is to edit /etc/yum.repos.d/glusterfs-epel.repo to globally change the version string "3.4.0" to "LATEST". Thanks, Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble Upgrading (Fedora)
Hey, - Original Message - > From: "Nicholas Kesick" > To: "oVirt Mailing List" > Sent: Friday, November 22, 2013 6:55:23 PM > Subject: [Users] Trouble Upgrading (Fedora) > > I am having trouble upgrading on Fedora 19 to 3.3.1. > > Two observations: > 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update. > > > 2) There is a dependency update circle involving > python-cpopen-1.2.3-4.fc19.x86_64 and dsm-python-cpopen.x86_64 > 0:4.13.0-11.fc19 This issue is fine. Not so smoothly but we had to do that. cpopen package is published as part of vdsm code in ovirt-3.3 and before, On master branch we require python-cpopen formal package that is shipped with fedora\rhel currently . Each time you'll switch between newer version of current master (3.4) to ovirt-3.3 or older you will notice this report > > Searching for ovirt-engine (after yum clear all) > yum list ovirt-engine > Loaded plugins: langpacks, refresh-packagekit, versionlock > Installed Packages > ovirt-engine.noarch 3.3.0-4.fc19 @ovirt-stable > > Next a the yum update > sudo yum history info 8 > Loaded plugins: langpacks, refresh-packagekit, versionlock > Transaction ID : 8 > Begin time : Thu Nov 21 18:28:24 2013 > Begin rpmdb : 1184:c12933940909ba00699a2269f2a08082654d7bdc > End time : 18:30:41 2013 (137 seconds) > End rpmdb : 1186:39b969c3d77367584456e993c37378e6e578a638 > User : root > Return-Code : Success > Command Line : update > Transaction performed with: > Installed rpm-4.11.1-3.fc19.x86_64 @updates > Installed yum-3.4.3-111.fc19.noarch @updates > Installed yum-plugin-versionlock-1.1.31-18.fc19.noarch @updates > Packages Altered: > Updated acl-2.2.51-9.fc19.x86_64 @fedora > Update 2.2.51-10.fc19.x86_64 @updates > Updated dbus-1:1.6.12-1.fc19.x86_64 @updates > Update 1:1.6.12-2.fc19.x86_64 @updates > Updated dbus-libs-1:1.6.12-1.fc19.x86_64 @updates > Update 1:1.6.12-2.fc19.x86_64 @updates > Updated gnutls-3.1.15-1.fc19.x86_64 @updates > Update 3.1.16-1.fc19.x86_64 @updates > Updated gnutls-dane-3.1.15-1.fc19.x86_64 @updates > Update 3.1.16-1.fc19.x86_64 @updates > Updated gnutls-utils-3.1.15-1.fc19.x86_64 @updates > Update 3.1.16-1.fc19.x86_64 @updates > Updated gtk2-2.24.22-1.fc19.x86_64 @updates > Update 2.24.22-2.fc19.x86_64 @updates > Updated iw-3.8-2.fc19.x86_64 @fedora > Update 3.11-1.fc19.x86_64 @updates > Install kernel-3.11.8-200.fc19.x86_64 @updates > Install kernel-modules-extra-3.11.8-200.fc19.x86_64 @updates > Updated libacl-2.2.51-9.fc19.x86_64 @fedora > Update 2.2.51-10.fc19.x86_64 @updates > Updated libvirt-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-client-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-config-network-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-config-nwfilter-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-interface-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-libxl-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-lxc-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-network-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-nodedev-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-nwfilter-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-qemu-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-secret-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-storage-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-uml-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-driver-xen-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-kvm-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-daemon-qemu-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-lock-sanlock-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Updated libvirt-python-1.0.5.6-3.fc19.x86_64 @updates > Update 1.0.5.7-2.fc19.x86_64 @updates > Up
Re: [Users] Trouble upgrading (was: oVirt 3.3.1 rlease)
Actually not, but thanks. There's a bug that's been discovered (and filed) regarding this release's VDSM compatibility with the RHEL 6.5 release which unfortunately coincided on the same day. Read the whole thread for details. -Bob On Nov 23, 2013 10:34 AM, "squadra" wrote: > http://www.ovirt.org/OVirt_3.3.1_release_notes > > will answer all your questions > > > On Thu, Nov 21, 2013 at 5: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 >> >> and also to a multilib version error due to vdsm-python 4.12 and 4.13. >> >> What's the proper upgrade procedure for a Host? >> >> Thanks, >> Bob >> >> On 11/21/2013 10:43 AM, Kiril Nesenko wrote: >> >>> The oVirt development team is very happy to announce the general >>> availability of oVirt 3.3.1 as of November 21th 2013. This release >>> solidifies oVirt as a leading KVM management application, and open >>> source alternative to VMware vSphere. >>> >>> oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 >>> (or similar). >>> >>> See release notes [1] for a list of the new features and bug fixed. >>> >>> [1] http://www.ovirt.org/OVirt_3.3.1_release_notes >>> >>> - Kiril >>> >>> ___ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > > > -- > > Sent from the Delta quadrant using Borg technology! > > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading (was: oVirt 3.3.1 rlease)
http://www.ovirt.org/OVirt_3.3.1_release_notes will answer all your questions On Thu, Nov 21, 2013 at 5: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 > > and also to a multilib version error due to vdsm-python 4.12 and 4.13. > > What's the proper upgrade procedure for a Host? > > Thanks, > Bob > > On 11/21/2013 10:43 AM, Kiril Nesenko wrote: > >> The oVirt development team is very happy to announce the general >> availability of oVirt 3.3.1 as of November 21th 2013. This release >> solidifies oVirt as a leading KVM management application, and open >> source alternative to VMware vSphere. >> >> oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 >> (or similar). >> >> See release notes [1] for a list of the new features and bug fixed. >> >> [1] http://www.ovirt.org/OVirt_3.3.1_release_notes >> >> - Kiril >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Sent from the Delta quadrant using Borg technology! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On Fri, Nov 22, 2013 at 12:36:41PM -0500, Bob Doolittle wrote: > > On 11/22/2013 11:45 AM, Dan Kenigsberg wrote: > >On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: > doesn't vdsm require vdsm-gluster which requires them? > >>>vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence > >>>if gluster server side functionality is being exercised, we would need > >>>to use EPEL packages. > >>> > >>>For a virt only cluster, only the client side packages are needed and > >>>RHEL 6.5 has these packages. > >>vijay - didn't we add gluster-cli for libgfapi support in core vdsm? > >glusterVolume uses the cli to only to tell if it's using tcp or rdma. > >This vdsm dependency is currently a soft one (not declared in the spec), > >and would only affect users which attempt to user true glusterfs storage > >domains without installing gluster-cli. > > This is not what I see. I see that vdsm.x86_64 has a dependency on > glusterfs-cli: > > # rpm -qa --whatrequires glusterfs-cli > vdsm-4.12.1-4.el6.x86_64 You are correct. My statement about vdsm's dependency is valid only for the not-yet-released rhev-3.3.0 (and thus, is not really apropriate for this venue). > Hence the problem, since the new version of glusterfs does not > deliver this package. I still think that your problem stems from mixing and matching epel-gluster repositories with rhs ones. It would be easier to deploy oVirt+epel-gluster and rhev+rhs. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble Upgrading (Fedora)
On 11/22/2013 06:55 PM, Nicholas Kesick wrote: I am having trouble upgrading on Fedora 19 to 3.3.1. Two observations: 1) I can't find ovirt-engine-3.3.1, even after a yum clear all; yum update. run engine-setup - it will unlock ovirt-engine and will handle backup/upgrade/etc. danken/yaniv/douglas? 2) There is a dependency update circle involving python-cpopen-1.2.3-4.fc19.x86_64 and vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 Searching for ovirt-engine (after yum clear all) yum list ovirt-engine Loaded plugins: langpacks, refresh-packagekit, versionlock Installed Packages ovirt-engine.noarch 3.3.0-4.fc19 @ovirt-stable Next a the yum update sudo yum history info 8 Loaded plugins: langpacks, refresh-packagekit, versionlock Transaction ID : 8 Begin time : Thu Nov 21 18:28:24 2013 Begin rpmdb: 1184:c12933940909ba00699a2269f2a08082654d7bdc End time :18:30:41 2013 (137 seconds) End rpmdb : 1186:39b969c3d77367584456e993c37378e6e578a638 User : root Return-Code: Success Command Line : update Transaction performed with: Installed rpm-4.11.1-3.fc19.x86_64 @updates Installed yum-3.4.3-111.fc19.noarch@updates Installed yum-plugin-versionlock-1.1.31-18.fc19.noarch @updates Packages Altered: Updatedacl-2.2.51-9.fc19.x86_64 @fedora Update 2.2.51-10.fc19.x86_64 @updates Updateddbus-1:1.6.12-1.fc19.x86_64 @updates Update 1:1.6.12-2.fc19.x86_64 @updates Updateddbus-libs-1:1.6.12-1.fc19.x86_64 @updates Update 1:1.6.12-2.fc19.x86_64 @updates Updatedgnutls-3.1.15-1.fc19.x86_64 @updates Update3.1.16-1.fc19.x86_64 @updates Updatedgnutls-dane-3.1.15-1.fc19.x86_64 @updates Update 3.1.16-1.fc19.x86_64 @updates Updatedgnutls-utils-3.1.15-1.fc19.x86_64 @updates Update 3.1.16-1.fc19.x86_64 @updates Updatedgtk2-2.24.22-1.fc19.x86_64 @updates Update 2.24.22-2.fc19.x86_64 @updates Updatediw-3.8-2.fc19.x86_64 @fedora Update3.11-1.fc19.x86_64 @updates Installkernel-3.11.8-200.fc19.x86_64 @updates Installkernel-modules-extra-3.11.8-200.fc19.x86_64 @updates Updatedlibacl-2.2.51-9.fc19.x86_64 @fedora Update2.2.51-10.fc19.x86_64 @updates Updatedlibvirt-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-client-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-config-network-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-config-nwfilter-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-interface-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-libxl-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-lxc-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-network-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-nodedev-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-nwfilter-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-qemu-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-secret-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-storage-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-uml-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-driver-xen-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-kvm-1.0.5.6-3.fc19.x86_64 @updates Update1.0.5.7-2.fc19.x86_64 @updates Updatedlibvirt-daemon-qemu-1.0.5.6-3.fc19.x86_64 @updates Update 1.0.
Re: [Users] Trouble upgrading
On 11/22/2013 12:52 PM, Vijay Bellur wrote: On 11/22/2013 11:18 PM, Bob Doolittle wrote: On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new repository, i
Re: [Users] Trouble upgrading
On 11/22/2013 11:18 PM, Bob Doolittle wrote: On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new repository, instead of reusing the old repository with new versioning? T
Re: [Users] Trouble upgrading
On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Vijay, Do you know why the glusterfs folks felt compelled to do a minor update of 3.4.0 to 3.4.1 utilizing an entirely new repository, instead of reusing the old repository with new versioning? That would have saved
Re: [Users] Trouble upgrading
On 11/22/2013 12:21 PM, Vijay Bellur wrote: On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay Yes. If I update the glusterfs-epel.repo file to use 3.4.1 instead of 3.4.0, yum is happy to do the update. Hopefully there are no incompatibilities in the interfaces consumed by vdsm. So the question is how to solv
Re: [Users] Trouble upgrading
On 11/22/2013 11:45 AM, Dan Kenigsberg wrote: On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli. This is not what I see. I see that vdsm.x86_64 has a dependency on glusterfs-cli: # rpm -qa --whatrequires glusterfs-cli vdsm-4.12.1-4.el6.x86_64 Hence the problem, since the new version of glusterfs does not deliver this package. -Bob "Luckily" we do not have this problem since we can only use gluster-fuse.. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 06:23 PM, Bob Doolittle wrote: On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. Would it be possible to update to glusterfs-3.4.1 by adding this repo? http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.1/RHEL/glusterfs-epel.repo Once the glusterfs packages are updated, the yum upgrade shouldn't break as glusterfs-3.4.0 is available in RHEL 6. -Vijay I'm wondering if the qemu issue I was when I tried --skip-broken is just an artifact of this, or some other issue entirely. We won't know until this glusterfs-cli issue is resolved. -Bob ___ Users mailing list Users@ovirt.org http://lis
Re: [Users] Trouble upgrading
On Fri, Nov 22, 2013 at 05:51:48PM +0200, Itamar Heim wrote: > >> > >>doesn't vdsm require vdsm-gluster which requires them? > > > >vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence > >if gluster server side functionality is being exercised, we would need > >to use EPEL packages. > > > >For a virt only cluster, only the client side packages are needed and > >RHEL 6.5 has these packages. > > vijay - didn't we add gluster-cli for libgfapi support in core vdsm? glusterVolume uses the cli to only to tell if it's using tcp or rdma. This vdsm dependency is currently a soft one (not declared in the spec), and would only affect users which attempt to user true glusterfs storage domains without installing gluster-cli. "Luckily" we do not have this problem since we can only use gluster-fuse.. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 11:21 AM, Vijay Bellur wrote: On 11/22/2013 01:00 PM, Itamar Heim wrote: On 11/22/2013 06:08 AM, Vijay Bellur wrote: 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 doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. vijay - didn't we add gluster-cli for libgfapi support in core vdsm? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 06:54 AM, Kristaps wrote: Bob Doolittle writes: 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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@... http://lists.ovirt.org/mailman/listinfo/users I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Thank you for confirming that this is indeed an issue. I was beginning to think it was just me somehow. I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1033587 to track this. I agree it seems to be a very big issue for RHEL 6 users. And we can't simply uninstall glusterfs-cli, as Vijay suggested, because it is required by vdsm. So I'm not seeing any easy workaround at the moment. I'm wondering if the qemu issue I was when I tried --skip-broken is just an artifact of this, or some other issue entirely. We won't know until this glusterfs-cli issue is resolved. -Bob ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
Bob Doolittle writes: > > > 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. > > Thanks, > Bob > > > > >> > >> Thanks, > >> Bob > >> > >>> > and also to a multilib version error due to vdsm-python 4.12 and 4.13. > > What's the proper upgrade procedure for a Host? > > Thanks, > Bob > > On 11/21/2013 10:43 AM, Kiril Nesenko wrote: > > The oVirt development team is very happy to announce the general > > availability of oVirt 3.3.1 as of November 21th 2013. This release > > solidifies oVirt as a leading KVM management application, and open > > source alternative to VMware vSphere. > > > > oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 > > (or similar). > > > > See release notes [1] for a list of the new features and bug fixed. > > > > [1] http://www.ovirt.org/OVirt_3.3.1_release_notes > > > > - Kiril > > > > ___ > > Users mailing list > > Users@... > > http://lists.ovirt.org/mailman/listinfo/users > > ___ > Users mailing list > Users@... > http://lists.ovirt.org/mailman/listinfo/users > >>> > >> > > > I'am experiencing same exact issue with upgrade on RHEL 6.4 and vdsm for oVirt installed. However, I did a little searching, and for me it seems it is like this: vds requires these glsuterfs packages to have the latest version: glusterfs glusterfs-api glusterfs-cli glusterfs-fuse glusterfs-libs In RHEL repository are these packages are with version 3.4.0.36rhs- 1.el6.x86_64 EXCEPT for glusterfs-cli, which RHEL repo doesn't have at all. oVirt repo has all those packages with version 3.4.0-8.el6.x86_64, which is older than RHEL repo packages. Hence, there is conflict. During vdsm update or even installation on RHEL 6.4 it tries to install the latest of all those packages. Looks likes this: glusterfs-3.4.0.36rhs-1.el6.x86_64 glusterfs-api-3.4.0.36rhs-1.el6.x86_64 glusterfs-fuse-3.4.0.36rhs-1.el6.x86_64 requires: glusterfs-libs-3.4.0.36rhs-1.el6.x86_64 glusterfs-cli-3.4.0-8.el6.x86_64 requires: glusterfs-libs-3.4.0-8.el6.x86_64 While this is not fixed, in my opinion, ovirt installation from repository on RHEL 6.4 is essentially broken. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 01:00 PM, Itamar Heim wrote: On 11/22/2013 06:08 AM, Vijay Bellur wrote: 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 doesn't vdsm require vdsm-gluster which requires them? vdsm requires vdsm-gluster only in gluster, gluster+virt clusters. Hence if gluster server side functionality is being exercised, we would need to use EPEL packages. For a virt only cluster, only the client side packages are needed and RHEL 6.5 has these packages. Thanks, Vijay ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
Hi, well we in Europe tend to sleep :) beside that: we don't run RHEL, but CentOS, and we didn't try upgrading our compute nodes until know. Am 22.11.2013 01:33, schrieb Bob Doolittle: > 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. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 06:08 AM, Vijay Bellur wrote: 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 doesn't vdsm require vdsm-gluster which requires them? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On 11/22/2013 02:55 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 ok, glusterfs and -libs exist. the matching cli doesn't. vijay - thoughts? 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 -Bob -Bob Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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 -Bob -Bob Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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? -Bob Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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. -Bob Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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) Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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. Thanks, Bob Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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? and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Trouble upgrading (was: oVirt 3.3.1 rlease)
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 and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
On Thu, Nov 21, 2013 at 6:57 PM, Itamar Heim wrote: > 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. BTW on rhel6 list today I saw several guys complaining about 6.5 repos already in place before official announce. So today and tomorrow updates for sure would get in 6.5 packages. One option is to register with rhsm and block release version with # subscription-manager register --username user_name --autosubscribe --release=6.4 (or from the web gui) So that you are sure not to get 6.5 packages until fixed/verified in oVirt. You can see available versions: # subscription-manager release --list 6.1 6.2 6.3 6.4 6Server <--- if this level is the one set (that is the default) the system would update to 6.5 when available # subscription-manager service-level --show Current service level: XXX (it doesn't work in 6.3, I don't know in 6.4) Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Trouble upgrading
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. Thanks, Bob and also to a multilib version error due to vdsm-python 4.12 and 4.13. What's the proper upgrade procedure for a Host? Thanks, Bob On 11/21/2013 10:43 AM, Kiril Nesenko wrote: The oVirt development team is very happy to announce the general availability of oVirt 3.3.1 as of November 21th 2013. This release solidifies oVirt as a leading KVM management application, and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.4 (or similar). See release notes [1] for a list of the new features and bug fixed. [1] http://www.ovirt.org/OVirt_3.3.1_release_notes - Kiril ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
