Bug 1685890

Summary: Upgrade from 4.2.8.2 fails with 'Constraint violation found in vm_interface (vmt_guid) |1'.
Product: [oVirt] ovirt-engine Reporter: Miguel Martin <mmartinv>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.1CC: bugs, michal.skrivanek, mperina, rbarry
Target Milestone: ovirt-4.3.3Flags: pm-rhel: ovirt-4.3+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-08 22:02:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miguel Martin 2019-03-06 09:02:25 UTC
Description of problem:

When running 'engine-setup' to upgrade the 'ovirt-engine' from version 4.2.8.2 to version 4.3.1.1 the process fails with the error 'Constraint violation found in  vm_interface (vmt_guid) |1'

Version-Release number of selected component (if applicable):
ovirt-engine-setup-plugin-ovirt-engine-4.3.1.1-1.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Try to upgrade from version 4.2.8.2 to 4.3.1.1 


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
         
[ INFO  ] Stage: Clean up
~~~~

Expected results:
The upgrade process finishes without errors

Additional info:

It looks like the same bug as https://bugzilla.redhat.com/show_bug.cgi?id=1528316

Comment 2 Michal Skrivanek 2019-03-07 04:40:15 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1547038#c6

IIUC a fix was made in 4.2 only by Eli, and 4.3 solution is not finalized yet? Ultimately a network team’s call?
Martine, is that correct or you have other thoughts? IMHO Should either be solved by Dominik’s bug or the same db workaround should be done in 4.3

Comment 3 Dominik Holler 2019-03-07 06:14:48 UTC
From my point of view, this is a duplicate of bug 1547038 which I try to fix now.

Comment 4 Miguel Martin 2019-03-07 08:18:53 UTC
(In reply to Michal Skrivanek from comment #2)
> https://bugzilla.redhat.com/show_bug.cgi?id=1547038#c6
> 
> IIUC a fix was made in 4.2 only by Eli, and 4.3 solution is not finalized
> yet? Ultimately a network team’s call?
> Martine, is that correct or you have other thoughts? IMHO Should either be
> solved by Dominik’s bug or the same db workaround should be done in 4.3

Dropping the constraints makes the upgrade to work but it's not possible to restore them after the upgrade or the engine-setup will fail if you try to run it again.

Comment 5 Dominik Holler 2019-03-08 22:02:23 UTC

*** This bug has been marked as a duplicate of bug 1547038 ***

Comment 6 Dominik Holler 2019-03-11 08:58:33 UTC

*** This bug has been marked as a duplicate of bug 1684586 ***