Bug 2070156 - [TESTONLY] Test upgrade from ovirt-engine-4.4.1
Summary: [TESTONLY] Test upgrade from ovirt-engine-4.4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Yedidyah Bar David
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-30 13:59 UTC by Yedidyah Bar David
Modified: 2022-05-26 16:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-26 16:23:55 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45496 0 None None None 2022-03-30 14:08:41 UTC
Red Hat Product Errata RHSA-2022:4711 0 None None None 2022-05-26 16:24:06 UTC

Description Yedidyah Bar David 2022-03-30 13:59:21 UTC
Description of problem:

I suspect upgrading from older 4.4 releases to 4.5 does not work well. Please test with the earliest 4.4 release - I think that's ovirt-engine-4.4.1.8. If it fails, we'll have to find the minimal version we can upgrade from and document that somehow/somewhere, perhaps also require/prevent in the rpm.

Comment 1 Yedidyah Bar David 2022-03-30 14:10:17 UTC
Some more details:

1. I had this (creating the bug) in my TODO list since two months ago. I wrote there "4.4.6", but right now do not remember why - likely I meant the minimum is 4.4.6, but I do not remember anymore. Sorry.

2. If we decide to prevent this, we'll have to patch both the engine's spec and engine-backup (to prevent restore on 4.5.0 a backup taken on e.g. 4.4.5, if we know it fails).

3. It's quite likely related to [1], which might have been related to [2][3], not clear.

[1] https://lists.ovirt.org/archives/list/users@ovirt.org/thread/DEPBIL2U6V4SM5QBG4SUCXDDLUGPHNXZ/

[2] https://bugzilla.redhat.com/1896359

[3] https://gerrit.ovirt.org/c/ovirt-dwh/+/114568/

Comment 2 Sandro Bonazzola 2022-03-30 14:36:14 UTC
4.4.1.8 was released the same day of 4.4.1.10 as 0-day. I think we can close this bug as not a bug as whoever tried to install RHV 4.4 at early days should have got 4.4.1.10 instead.
Also 4.4.1 was released over 1 year ago. I would rather spend time covering more common cases rather than this upgrade path.

Comment 3 Yedidyah Bar David 2022-03-31 05:02:49 UTC
(In reply to Sandro Bonazzola from comment #2)
> 4.4.1.8 was released the same day of 4.4.1.10 as 0-day. I think we can close
> this bug as not a bug as whoever tried to install RHV 4.4 at early days
> should have got 4.4.1.10 instead.

Summary line says 4.4.1, not  4.4.1.8 :-)

> Also 4.4.1 was released over 1 year ago. I would rather spend time covering
> more common cases rather than this upgrade path.

Please see comment 1. If you prefer to "just" write 4.4.5, that's just fine
with me. If it then fails, we'll have to decide what to do.

Personally I am not sure that "4.4.1 was released over 1 year ago" is relevant
here. I think people that did install it and remained there because it was
good enough for their needs, are still likely to upgrade to "4.4 SP1".

Obviously, more so for 4.4.5.

Ideally, I'd like us to test upgrade between each officially-supported
combination of versions.

Comment 14 errata-xmlrpc 2022-05-26 16:23:55 UTC
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 (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), 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-2022:4711


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