On Tue, Jul 31, 2012 at 1:55 PM, Ofer Schreiber <oschreib(a)redhat.com> wrote:
> you need to run the upgrade script since the setup locks the
rpm's to
> make sure the code isn't updated without updating the db in sync
we're using yum versionlock in order to prevent unintended upgrades.
just run engine-upgrade.
Hi again,
When running engine-upgrade I received the following message...
12 Updates available:
* ovirt-engine-3.1.0-3.15.el6.noarch
* ovirt-engine-backend-3.1.0-3.15.el6.noarch
* ovirt-engine-config-3.1.0-3.15.el6.noarch
* ovirt-engine-dbscripts-3.1.0-3.15.el6.noarch
* ovirt-engine-genericapi-3.1.0-3.15.el6.noarch
* ovirt-engine-notification-service-3.1.0-3.15.el6.noarch
* ovirt-engine-restapi-3.1.0-3.15.el6.noarch
* ovirt-engine-setup-3.1.0-3.15.el6.noarch
* ovirt-engine-tools-common-3.1.0-3.15.el6.noarch
* ovirt-engine-userportal-3.1.0-3.15.el6.noarch
* ovirt-engine-webadmin-portal-3.1.0-3.15.el6.noarch
* vdsm-bootstrap-4.10.0-0.191.9.el6.noarch
Error: New ovirt-engine-setup rpm available via yum.
Please execute `yum update ovirt-engine-setup`, then re-execute
'engine-upgrade'.
To use the current ovirt-engine-setup rpm, execute 'engine-upgrade
--force-current-setup-rpm'.
...I tried running yum update ovirt-engine-setup as it said, but this
finds no package to upgrade, should I try running the 'engine-upgrade
--force-current-setup-rpm' or is there something else I should rather
do?
Any thoughts on this?
Thanks again.
Regards.
Neil Wilson.