[ovirt-users] Re: Backup & Restore

On 19.12.2018 11:54, Yedidyah Bar David wrote: Thanks, removed. 20171231170651 is most probably the date when we installed the last major release (4.2.0). We did a lot more updates since and I now have a suspicion what went wrong here. We naively assumed that a yum update is sufficient for a minor upgrade of the engine installation. Rereading the documentation I think we were missing explicit engine-setup calls after each minor upgrade. It may be the case, that the extra call to engine-setup is required to not be part of the yum update. I think in this case it would be a good idea to warn users that this step has not yet been taken and the update is not completed yet. Could this be the cause for the missing logs and behavior discrepancies? If yes, would another call to engine-setup in the current state fix this and allow us to produce correct backups in the future? I currently fear that would only cure the symptom. I don't think this is necessary. You are right, we did this. Best regards Torsten >> >> There was indeed one glitch during updates which was connected to the >> Postgres version in use: >> >> The initial install was (accidentally) done under Postgres 9.4 which >> happened to be present on the machine at that point of time. oVirt 4.0 >> was allowing this way back then. I think in 4.1 Postgres 9.2 has been >> enforced, so there had been workarounds to allow updates under 9.4. This >> got resolved with the migration to 4.2 which brought the Postgres 9.5 >> installation (if I recall that correctly). >> >> Other than that I have no idea which might have introduced this. > > All of this sounds irrelevant to current problem. Thanks for recalling :-) > > Best regards, > >> >> If you find something in the logs you need more information on, please >> let me know. >> >> Best regards >> >> Torsten >> >> >>> If you, or anyone, manages to come up with a flow resulting in a 4.2 >>> engine database that contains a function uuid_generate_v1 in the engine >>> database schema, I'd definitely want to know about it. >>> >>> Re-adding others posting in this thread, in case someone has a clue. >>> Perhaps one of you has setup logs of the machine on which the backup >>> was generated? If so, please share. Thanks. >>> >>> That said, on a second thought, the implications of this are not that >>> significant - mainly somewhat lower performance - so perhaps it's more >>> important to fix your bug (by adding a line to IGNORED_ERRORS, as you >>> suggested)... but it's still weird. >>> >>> Thanks and best regards, >>> >>>> >>>> Cheers, >>>> >>>> Torsten >>>> >>>> >>>> On 18.12.2018 07:54, Yedidyah Bar David wrote: >>>>> On Mon, Dec 17, 2018 at 2:26 PM Torsten Stolpmann >>>>> <torsten.stolpmann(a)verit.de&gt; wrote: >>>>>> >>>>>> I experienced the same issue while restoring a full backup (engine & >>>>>> dwh) on a clean machine. Both machines are running CentOS 7.6 and >>>>>> oVirt 4.2.7. >>>>>> >>>>>> The issue went away when adding the following line to the IGNORED_ERRORS >>>>>> list starting at 1944 in engine-backup: >>>>>> >>>>>> must be owner of function uuid_generate_v1 >>>>>> >>>>>> Hope this helps, >>>>> >>>>> It does, and thanks for the report! >>>>> >>>>> Can you please share all of your setup logs (/var/log/ovirt-engine/setup/*)? >>>>> >>>>> Thanks! >>>>> >>>>> More details: >>>>> >>>>> This function should not normally be included in a 4.2 backup, and I do >>>>> not yet understand why you get this error. >>>>> >>>>> If it's a clean 4.2 setup, it should never have been defined. >>>>> Earlier versions did create it, and the upgrade process should have >>>>> dropped it, if it's an upgraded setup. See also: >>>>> >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1515635 >>>>> >>>>> Best regards, >>>>> >>>>>> >>>>>> Torsten >>>>>> >>>>>> On 24.05.2018 11:32, emmanuel.thetas(a)obs-nancay.fr wrote: >>>>>>> hi, >>>>>>> >>>>>>> I have the same error when I try to restore on a new hosted VM (ovirt 4.2.3) >>>>>>> Have you a solution ? >>>>>>> >>>>>>> Emmanuel >>>>>>> _______________________________________________ >>>>>>> Users mailing list -- users(a)ovirt.org >>>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)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/YMMFCYUMLCM... >>>>> >>>>> >>>>> >>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)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/FCN5WVAJOGF... >>> >>> >>> > > >