It all got a bit messy, but that's probably down to me.

  I removed the 'old' ovirt repo definitions after I installed the 4.2 pre release repo (simply because yum was complaining about multiple definitions).

  I also allowed the installer to clean-up the old database directory, which it did.

  The updated PostgreSQL server stayed up and running which stopped 4.1 from starting the version of PostgreSQL that it wanted running (port in use I expect) etc etc etc

So no in this particular case roll back failed, but there are a bunch of warnings issued but engine-setup that that would probably happen.

I've attached the engine-setup-log as requested.

Best regards,

Brett

On 29 September 2017 at 07:24, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

2017-09-28 20:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:

Thanks Tomas,

  I'm restoring backup at the moment, I'll let you know how it goes when on the next attempt.

Didn't the setup rollback automatically? Can you please share the setup logs?

 

On 28 September 2017 at 18:46, Tomas Jelinek <tjelinek@redhat.com> wrote:

Hey Brett,

That is strange - it looks like you have some VM which has memory size larger than the max memory size.

You need to go over your VMs / templates to find which one has this wrong config and change it.

Alternatively, to find it faster if you have many vms/templates, you could run this SQL query against your engine database:
select vm_name from vm_static where mem_size_mb > max_memory_size_mb;

Tomas

On Thu, Sep 28, 2017 at 6:07 PM, Maton, Brett <matonb@ltresources.co.uk> wrote:

Upgrading from oVirt 4.1.7

hosted-engine VM:

4GB RAM

hosted-engine setup failed, setup log shows this error:

Running upgrade sql script '/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql'...

2017-09-28 16:56:22,951+0100 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20170928164338-0rkilb.log', '-c', 'apply'] stderr:
psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql:2: ERROR:  check constraint "vm_static_max_memory_size_lower_bound" is violated by some row
FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql

2017-09-28 16:56:22,951+0100 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:374 schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql
2017-09-28 16:56:22,952+0100 DEBUG otopi.context context._executeMethod:143 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 376, in _misc
    raise RuntimeError(_('Engine schema refresh failed'))
RuntimeError: Engine schema refresh failed

What's the minimum RAM required now ?

Regards,

Brett

_______________________________________________
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

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.