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
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
Thanks Tomas, I'm restoring backup at the moment, I'll let you know how it goes when on the next attempt. 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/dbscr ipts/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
oooo, it was the hosted engine itself. RAM 4096 Max RAM 0 I don't think I've touched the system settings on the hosted engine vm itself though. This (testlab) cluster was originally installed with 4.0 (I think) and gets constantly upgraded with the pre-releases... After a bit of faffing around to clean up leftovers of the failed upgrade, I'm now running v4.2.0 and it's certianly different :) I did have one firefox browser that refused to load the dashboard reporting 500 errors, but that appears to have been down to cached content (on OS X). I look forward to playing with the new UI. Thanks, Brett On 28 September 2017 at 19:29, Maton, Brett <matonb@ltresources.co.uk> wrote:
Thanks Tomas,
I'm restoring backup at the moment, I'll let you know how it goes when on the next attempt.
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/dbscr ipts/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-s etup/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
2017-09-28 21:38 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
oooo, it was the hosted engine itself.
RAM 4096 Max RAM 0
I don't think I've touched the system settings on the hosted engine vm itself though.
This (testlab) cluster was originally installed with 4.0 (I think) and gets constantly upgraded with the pre-releases...
Thanks for running oVirt pre-releases in your testlab! Simone, Martin, can you please follow up on this?
After a bit of faffing around to clean up leftovers of the failed upgrade,
I'm now running v4.2.0 and it's certianly different :)
Great to see you managed to upgrade to 4.2.0 alpha!
I did have one firefox browser that refused to load the dashboard reporting 500 errors, but that appears to have been down to cached content (on OS X).
Greg. any clue? If I understood it correctly, you've been able to access the dashboard from some browser but failed on one firefox instance right?
I look forward to playing with the new UI.
Thanks, Brett
On 28 September 2017 at 19:29, Maton, Brett <matonb@ltresources.co.uk> wrote:
Thanks Tomas,
I'm restoring backup at the moment, I'll let you know how it goes when on the next attempt.
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
On Fri, Sep 29, 2017 at 2:30 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-28 21:38 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
oooo, it was the hosted engine itself.
RAM 4096 Max RAM 0
I don't think I've touched the system settings on the hosted engine vm itself though.
This (testlab) cluster was originally installed with 4.0 (I think) and gets constantly upgraded with the pre-releases...
Thanks for running oVirt pre-releases in your testlab! Simone, Martin, can you please follow up on this?
After a bit of faffing around to clean up leftovers of the failed upgrade,
I'm now running v4.2.0 and it's certianly different :)
Great to see you managed to upgrade to 4.2.0 alpha!
I did have one firefox browser that refused to load the dashboard reporting 500 errors, but that appears to have been down to cached content (on OS X).
Greg. any clue? If I understood it correctly, you've been able to access the dashboard from some browser but failed on one firefox instance right?
Perhaps we should advise in Release Notes to clear cache.
I look forward to playing with the new UI.
Thanks, Brett
On 28 September 2017 at 19:29, Maton, Brett <matonb@ltresources.co.uk> wrote:
Thanks Tomas,
I'm restoring backup at the moment, I'll let you know how it goes when on the next attempt.
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
-- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
Hmm, let me see if there's another setup log.... It was the SQL issue that caused the real problem, running out of space during yum updates on my 'tiny' hosted engine vm isn't that uncommon... On 29 September 2017 at 08:41, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M
We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
That log appears to be the only one I have, the more recent ones are the restore and then successful install of 4.2. I just checked yum.conf and no, keepcache is off (0) I didn't see any errors when engine-setup downloaded the packages, it failed/stopped during the db migration / upgrade. Brett On 29 September 2017 at 08:41, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M
We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr ipts/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-s etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
2017-09-29 9:58 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
That log appears to be the only one I have, the more recent ones are the restore and then successful install of 4.2.
I just checked yum.conf and no, keepcache is off (0)
I didn't see any errors when engine-setup downloaded the packages, it failed/stopped during the db migration / upgrade.
Yes, sorry, the out of space error is happening in the rollback from the failure during the database migration.
Brett
On 29 September 2017 at 08:41, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M
We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr > ipts/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-s > etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
Ah ok, So assuming there was enough space the rollback should have put the engine back to it's previous state. On 29 September 2017 at 09:38, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:58 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
That log appears to be the only one I have, the more recent ones are the restore and then successful install of 4.2.
I just checked yum.conf and no, keepcache is off (0)
I didn't see any errors when engine-setup downloaded the packages, it failed/stopped during the db migration / upgrade.
Yes, sorry, the out of space error is happening in the rollback from the failure during the database migration.
Brett
On 29 September 2017 at 08:41, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M
We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr >> ipts/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-s >> etup/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
2017-09-29 11:21 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
Ah ok,
So assuming there was enough space the rollback should have put the engine back to it's previous state.
Yes, it should have worked.
On 29 September 2017 at 09:38, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:58 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
That log appears to be the only one I have, the more recent ones are the restore and then successful install of 4.2.
I just checked yum.conf and no, keepcache is off (0)
I didn't see any errors when engine-setup downloaded the packages, it failed/stopped during the db migration / upgrade.
Yes, sorry, the out of space error is happening in the rollback from the failure during the database migration.
Brett
On 29 September 2017 at 08:41, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2017-09-29 9:29 GMT+02:00 Maton, Brett <matonb@ltresources.co.uk>:
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.
Thanks! I see that the failure is: YumDownloadError: Errors were encountered while downloading packages. ovirt-engine-wildfly-10.1.0-1.el7.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/7/ovirt-4.1/packages * free 67 M * needed 130 M
We may consider to run "yum clean packages" before starting rollback to free space there. Did you have keepcache=1 in your yum.conf?
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/dbscr >>> ipts/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 <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>
participants (4)
-
Greg Sheremeta -
Maton, Brett -
Sandro Bonazzola -
Tomas Jelinek