Bug 1750657 - revert workaround for fk conflict
Summary: revert workaround for fk conflict
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dominik Holler
QA Contact: Daniel Gur
URL:
Whiteboard:
Depends On: 528316 1547038 1684586
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-10 07:44 UTC by Dominik Holler
Modified: 2020-07-01 09:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-28 12:42:43 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109330 0 master MERGED db: reminder to remove workaround 2020-07-01 09:26:49 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.