As the potential user could upgrade from an older version, though not
recommended to stay too much below, I simulate this upgrade from 4.2.3.7
(current engine package version is ovirt-engine-4.2.3.7-1.el7.noarch
updated on 26/05) to 4.2.5 and I get this in engine-setup
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20180803141347.gdQfiz.dump'.
[ INFO ] Creating/refreshing Engine database schema
[ ERROR ] schema.sh: FATAL: Cannot execute sql command:
--file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_1210_add_foreign_key_to_image_transfers.sql
[ ERROR ] Failed to execute stage 'Misc configuration': Engine schema
refresh failed
[ INFO ] Yum Performing yum transaction rollback
[ INFO ] Restoring file
'/var/lib/ovirt-engine/backups/engine-20180803141347.gdQfiz.dump' to
database localhost:engine.
[ ERROR ] Errors while restoring engine database, please check the log file
for details
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20180803140934-1thg3k.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20180803141603-setup.conf'
[WARNING] Rollback of DWH database started
This might be a long process, but it should be safe to start the
engine service before it finishes, if needed.
[ INFO ] Clearing DWH database ovirt_engine_history
[ INFO ] Restoring DWH database ovirt_engine_history
[ INFO ] Restoring file
'/var/lib/ovirt-engine-dwh/backups/dwh-20180803141340.cQoOU2.dump' to
database localhost:ovirt_engine_history.
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
[root@ovirt ~]#
Until fixed what would be the step to resolve, as also the restore of
database failed?
What can I do to restore/clean/upgrade again?
BTW: it is a self hosted engine
Thanks,
Gianluca
On Fri, Aug 3, 2018 at 2:14 PM, Jan Siml <js...@plusline.net> wrote:
> Hello,
>
> There are probably some more stale image transfers records,
>> can you please check whether 'image_transfers' table is empty?
>> If not, you can try removing them by executing:
>> "DELETE FROM image_transfers WHERE command_id NOT IN (SELECT
>> command_entities.command_id FROM command_entities);"
>> (you can simply prepend it to '04_02_1210_add_foreign_key_to
>> _image_transfers.sql')
>>
>
> that's how it worked and the update was successful. Thanks!
>
> Regards
>
> Jan
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/communit
> y/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archiv
> es/list/users@ovirt.org/message/RQS4MHPWU7HWCZH6BIELHVGPB4BMBBGL/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/QVU7OITP3ZWIZZHO2AWBWM63P7ZKTGEC/
