On Fri 08 Feb 2013 10:27:15 AM IST, Karli Sjöberg wrote:
Hi,
my engine have these packages installed after a yum update:
# rpm -qa | grep ovirt-engine | sort -n
ovirt-engine-3.1.0-2.fc17.noarch
ovirt-engine-backend-3.1.0-2.fc17.noarch
ovirt-engine-cli-3.2.0.5-1.fc17.noarch
ovirt-engine-config-3.1.0-2.fc17.noarch
ovirt-engine-dbscripts-3.1.0-2.fc17.noarch
ovirt-engine-genericapi-3.1.0-2.fc17.noarch
ovirt-engine-notification-service-3.1.0-2.fc17.noarch
ovirt-engine-restapi-3.1.0-2.fc17.noarch
ovirt-engine-sdk-3.2.0.2-1.fc17.noarch
ovirt-engine-setup-3.1.0-4.fc17.noarch
ovirt-engine-tools-common-3.1.0-2.fc17.noarch
ovirt-engine-userportal-3.1.0-2.fc17.noarch
ovirt-engine-webadmin-portal-3.1.0-2.fc17.noarch
And when issuing check update:
# yum check-update
...
ovirt-engine-dbscripts.noarch 3.1.0-4.fc17
ovirt-stable
But from any other machine, like my laptop or any other Host all
packages show up with version "3.1.0-4.fc17 ". Look at this:
the engine# yum list ovirt-engine*
...
Installed packages
ovirt-engine.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-backend.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-cli.noarch
3.2.0.5-1.fc17 @updates
ovirt-engine-config.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-dbscripts.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-genericapi.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-notification-service.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-restapi.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-sdk.noarch
3.2.0.2-1.fc17 @updates
ovirt-engine-setup.noarch
3.1.0-4.fc17 @ovirt-engine-3.1
ovirt-engine-tools-common.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-userportal.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
ovirt-engine-webadmin-portal.noarch
3.1.0-2.fc17 @ovirt-engine-3.1
Available packages
ovirt-engine-dbscripts.noarch
3.1.0-4.fc17 ovirt-stable
ovirt-engine-iso-uploader.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-javadoc.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-log-collector.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-setup-plugin-allinone.noarch
3.1.0-4.fc17 ovirt-stable
a Host# yum list ovirt-engine*
...
Available packages
ovirt-engine.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-backend.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-cli.noarch
3.1.0.6-1.fc17 ovirt-engine-3.1
ovirt-engine-config.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-dbscripts.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-genericapi.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-iso-uploader.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-javadoc.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-log-collector.noarch
3.0.0.0001-15.fc17 updates
ovirt-engine-notification-service.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-restapi.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-sdk.noarch
3.1.0.4-1.fc17 ovirt-engine-3.1
ovirt-engine-setup.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-setup-plugin-allinone.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-tools-common.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-userportal.noarch
3.1.0-4.fc17 ovirt-engine-3.1
ovirt-engine-webadmin-portal.noarch
3.1.0-4.fc17 ovirt-engine-3.1
And I can´t seem persuade my engine otherwise. There are lots of
updates available and now engine doesn´t run because of these version
inconsistencies! I have tried "yum clean all" and tried to rerun but
my engine still doesn´t think there are any updates available. I
noticed that my repo file slightly differed from what´s in the one
that gets installed by the repo.rpm at
ovirt.org so I changed it to
exactly match it, but to no avail. What can I do?
Best Regards
Karli Sjöberg
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Karli
As soon as engine is installed, it's rpm's are locked within yum, and
are not visible for manual upgrade. It is done to prevent updating RPMs
separately and not as an application.
If all you want is to upgrade engine, simply run 'engine-upgrade'.
Let us know how it goes.
--
Alex Lourie.