Bug 2070156
| Summary: | [TESTONLY] Test upgrade from ovirt-engine-4.4.1 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yedidyah Bar David <didi> |
| Component: | ovirt-engine | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED ERRATA | QA Contact: | Guilherme Santos <gdeolive> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5.0 | CC: | gdeolive, sbonazzo |
| Target Milestone: | ovirt-4.5.0 | Keywords: | TestOnly, ZStream |
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-26 16:23:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yedidyah Bar David
2022-03-30 13:59:21 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/ 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. (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. 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 |