On Tue, Jul 31, 2012 at 1:04 PM, Itamar Heim <iheim@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
Thanks Itamar, I see after running engine-check-update I get.. 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 Can this update be done on a live system with multiple hosts running? I'm currently running the engine on one of the nodes, which I know isn't ideal. I've searched a bit regarding the upgrade procedures from 3.1 to 3.1, does the DB need backing up, are there any wiki pages on the correct steps? Thanks very much. Regards. Neil Wilson.