That must be what happened, even though I didn't see any error messages. One of
my colleagues installed 4.5.7 in a virtualbox VM and then spent some time
comparing the databases. He was able to insert the missing items from the newer
installation into our engine database and that seems to have fixed the issues.
There was more missing from the database than just the MigrationPolicies row.
I'm not sure how much was missing. The error messages would change when he
added an item, he would diagnose the message, add another item, and repeat.
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/37ZWMKR6WY6F7CYAJT3MSBK2LATGYYHV/
