+++ 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.
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.
Is this a bug or a feature?
This is technical debt of normalizing the db and aligning the engine accordingly, with no customer facing effects (hopefully...)
This seems like a risky change with limited benefit, therefore for now.
*** Bug 1684586 has been marked as a duplicate of this bug. ***
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
*** Bug 1685890 has been marked as a duplicate of this bug. ***
Removing CodeChange and updating title as this is an upgrade blocker
Ahh, sorry I've missed that we have BZ1684586 to track that issue in 4.3
*** Bug 1687707 has been marked as a duplicate of this bug. ***
QE is required to test ovirt-dwh to ensure the related code change does not introduce regressions.
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
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.