Bug 1750657

Summary:	revert workaround for fk conflict
Product:	[oVirt] ovirt-engine	Reporter:	Dominik Holler <dholler>
Component:	Setup.Engine	Assignee:	Dominik Holler <dholler>
Status:	CLOSED DEFERRED	QA Contact:	Daniel Gur <dagur>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	future	CC:	bugs, michal.skrivanek, mperina
Target Milestone:	---	Flags:	pm-rhel: ovirt-4.5?
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:	2020-05-28 12:42:43 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:
Bug Depends On:	528316, 1547038, 1684586
Bug Blocks:

Description Dominik Holler 2019-09-10 07:44:11 UTC

oVirt 4.2 and 4.3 contains a workaround (bug 1528316 and bug 1684586) for bug 1547038.
To remove the workaround, the fix of 1547038 has to be applied to the db, which is true for all databases of oVirt 4.4.
For this reason, the workaround can be removed on oVirt 4.5.

Comment 1 Michal Skrivanek 2020-03-18 15:29:29 UTC

note we're not supporting upgrade from 4.3 to 4.4, it's a backup/restore procedure.
Do you still want to revert anything?

Comment 2 Dominik Holler 2020-05-28 09:30:38 UTC

(In reply to Michal Skrivanek from comment #1)
> note we're not supporting upgrade from 4.3 to 4.4, it's a backup/restore
> procedure.
> Do you still want to revert anything?

Yes, I am not brave enough to change our current approach.

Comment 3 Sandro Bonazzola 2020-07-01 09:28:20 UTC

This bug is closed deferred but it has a patch included in ovirt-engine referencing this bug past its closure.
has this bug been handled?

Comment 4 Dominik Holler 2020-07-01 09:30:56 UTC

(In reply to Sandro Bonazzola from comment #3)
> This bug is closed deferred but it has a patch included in ovirt-engine
> referencing this bug past its closure.
> has this bug been handled?

The patch is just the comment:
TODO remove this workaround as soon as no upgrade from 4.3 is supported anymore

From my point of view the state of the bug is correct.