+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1547038 +++ ====================================================================== +++ This bug was initially created as a clone of Bug #1528316 +++ As explained in https://bugzilla.redhat.com/show_bug.cgi?id=1528316#c4 our vm_interface has two fields (vm_guid and vmt_guid) referring to the same table, and we should eliminate this. (Originally by danken)
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. (Originally by rule-engine)
Is this a bug or a feature? (Originally by Yaniv Kaul)
This is technical debt of normalizing the db and aligning the engine accordingly, with no customer facing effects (hopefully...) (Originally by Eitan Raviv)
This seems like a risky change with limited benefit, therefore for now. (Originally by ylavi)
*** Bug 1684586 has been marked as a duplicate of this bug. *** (Originally by Dominik Holler)
Steps to Reproduce on oVirt 4.3: 1. Create a VM with a vNIC 2. Create a template of this VM 3. Create a subversion of the template 4. Run engine-setup Actual results: [ INFO ] Checking the Engine database consistency [ ERROR ] Failed to execute stage 'Setup validation': Failed checking Engine database: an exception occurred while validating the Engine database, please check the logs for getting more info: Constraint violation found in vm_interface (vmt_guid) |1 Expected results: engine-setup succeeds (Originally by Dominik Holler)
*** Bug 1685890 has been marked as a duplicate of this bug. *** (Originally by Dominik Holler)
Removing CodeChange and updating title as this is an upgrade blocker (Originally by Martin Perina)
Ahh, sorry I've missed that we have BZ1684586 to track that issue in 4.3 (Originally by Martin Perina)
*** Bug 1687707 has been marked as a duplicate of this bug. *** (Originally by Martin Perina)
Verified on - rhvm-4.4.0-0.4.master.el7.noarch rhvm-4.3.7.0-0.1.el7.noarch >> rhvm-4.4.0-0.4.master.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:0498