cloning to oVirt to bypass the annoying process +++ This bug was initially created as a clone of Bug #1382746 +++ Description of problem: Tried to upgrade from latest 3.6 release to latest 4.0 release. Database dump imports without error, but engine-setup fails. [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0140_convert_memory_snapshots_to_disks.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed Version-Release number of selected component ): ovirt-engine-setup-base-4.0.4.4-0.1.el7ev.noarch ovirt-engine-dbscripts-4.0.4.4-0.1.el7ev.noarch --- Additional comment from Arik on 2016-10-09 11:37:05 CEST --- Yep, there's a bug when active snapshots contain memory during the upgrade to 4.0. Chris, if you want to upgrade without waiting for a fix then the problematic VM is 'rhel6-test1', you can simply start and stop it and then do the upgrade. --- Additional comment from Arik on 2016-10-09 11:49:31 CEST --- steps to reproduce: 1. create snapshot with memory in 3.6 2. shutdown the VM 3. preview the snapshot 4. commit to the snapshot 5. remove the snapshot (optional step, that is just to better simulate the state that is reported in this bug). 6. upgrade to 4.0
verified in ovirt-engine-4.0.5.2-0.2.el7ev.noarch used reproduction steps from Description and multiple snapshots