Description of problem: After enabling oVirt 3.4.1 RC on Fedora 19, engine-setup doesn't detect available updates. Version-Release number of selected component (if applicable): otopi-1.2.1-0.0.master.20140417.git167d209.fc19.noarch otopi-java-1.2.1-0.0.master.20140417.git167d209.fc19.noarch ovirt-engine-3.4.0-1.fc19.noarch ovirt-engine-backend-3.4.0-1.fc19.noarch ovirt-engine-cli-3.4.0.5-1.fc19.noarch ovirt-engine-dbscripts-3.4.0-1.fc19.noarch ovirt-engine-lib-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-restapi-3.4.0-1.fc19.noarch ovirt-engine-sdk-python-3.4.1.0-1.fc19.noarch ovirt-engine-setup-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-setup-base-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-setup-plugin-ovirt-engine-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-setup-plugin-ovirt-engine-common-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-setup-plugin-websocket-proxy-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-engine-tools-3.4.0-1.fc19.noarch ovirt-engine-userportal-3.4.0-1.fc19.noarch ovirt-engine-webadmin-portal-3.4.0-1.fc19.noarch ovirt-engine-websocket-proxy-3.4.1-0.0.master.20140423010335.git3308ac3.fc19.noarch ovirt-host-deploy-1.2.1-0.0.master.20140422120209.git9e4b7c0.fc19.noarch ovirt-host-deploy-java-1.2.1-0.0.master.20140422120209.git9e4b7c0.fc19.noarch ovirt-image-uploader-3.4.1-0.0.master.20140416.gitc344927.fc19.noarch ovirt-iso-uploader-3.4.1-0.0.master.20140416.git7681f8b.fc19.noarch ovirt-log-collector-3.4.2-0.0.master.20140416.gitf967da2.fc19.noarch ovirt-release34-1.0.0-0.1.master.noarch vdsm-4.14.7-0.fc19.x86_64 vdsm-cli-4.14.7-0.fc19.noarch vdsm-python-4.14.7-0.fc19.x86_64 vdsm-python-zombiereaper-4.14.7-0.fc19.noarch vdsm-xmlrpc-4.14.7-0.fc19.noarch How reproducible: 100% on F19. Steps to Reproduce: 1. on F19 install ovirt-engine using 3.4 stable repository 2. yum update 3. enable 3.4 rc repo as in: http://www.ovirt.org/OVirt_3.4.1_release_notes 4. yum update 5. engine-setup Actual results: engine-setup doesn't detect updates. #yum --disableplugin=versionlock check-update Loaded plugins: langpacks, refresh-packagekit ovirt-engine.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-backend.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-dbscripts.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-restapi.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-tools.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-userportal.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc ovirt-engine-webadmin-portal.noarch 3.4.1-0.0.master.20140423010335.git3308ac3.fc19 ovirt-3.4-rc Expected results: engine-setup detects upgrade Additional info: # cat /etc/yum/pluginconf.d/versionlock.list ovirt-engine-3.4.0-1.fc19.noarch ovirt-engine-backend-3.4.0-1.fc19.noarch ovirt-engine-dbscripts-3.4.0-1.fc19.noarch ovirt-engine-restapi-3.4.0-1.fc19.noarch ovirt-engine-tools-3.4.0-1.fc19.noarch ovirt-engine-userportal-3.4.0-1.fc19.noarch ovirt-engine-webadmin-portal-3.4.0-1.fc19.noarch
If it may help, from #ovirt about this issue: (15:19:30) SvenKieske: sbonazzo: i did a direct upgrade from 3.3.3 to 3.3.5 and then 3.4.1 RC, went well, aside some json api incompatibilities
well I may add: I did it on CentOS 6.5, not on Fedora. And I did ran into some issues regarding the new gpg key for ovirt.org repo, which I installed by hand (shouldn't the key also get shipped/autoinstalled)?
Please attach setup log.
Created attachment 892446 [details] 3.4.0 initial setup Initial setup of oVirt 3.4.0 from stable repo.
Created attachment 892447 [details] engine-setup for upgrading to 3.4.1-rc logs from engine-setup run using 3.4.1 RC repository (http://resources.ovirt.org/pub/ovirt-3.4-rc/)
This is related to the group, I thought we remove this from upstream in favor of alternate solution (bug#1084489). 2014-05-02 14:54:08 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages packages.verbose:178 Yum: queue group ovirt-engine-3.4 for update 2014-05-02 14:54:08 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages packages.verbose:178 Yum: group ovirt-engine-3.4 queued
(In reply to Alon Bar-Lev from comment #6) > This is related to the group, I thought we remove this from upstream in > favor of alternate solution (bug#1084489). > > 2014-05-02 14:54:08 DEBUG > otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages > packages.verbose:178 Yum: queue group ovirt-engine-3.4 for update > 2014-05-02 14:54:08 DEBUG > otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages > packages.verbose:178 Yum: group ovirt-engine-3.4 queued Adding Kiril and David. I can't see the group info neither in 3.4 stable nor in 3.4-rc repos so I'm not sure it is related. Kiril, David, please verify that you're not using groups in above repositories.
try to list available groups using yum. see why the code detects that group is available. the miniyum first lists available groups, then queue the group.
I can confirm that there are no groups created on that repo, maybe it's using the old cache?
Closing as duplicate of bug 1084489. Also if the group wasn't available from inside the repositories, ovirt-engine-3.4 was still around on my system as installed with no packages and visible running # yum grouplist Also, trying to remove the group with: # yum groupremove ovirt-engine-3.4 did not remove the group. I had to use: # yum groups mark remove ovirt-engine-3.4 In order to get rid of it and re-enable the upgrade feature. *** This bug has been marked as a duplicate of bug 1084489 ***