Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1503196

Summary:	Upgrade to 4.2 from < 4.1.7 fails
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Packaging.rpm	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	bugs, lsvaty, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.0
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:	2017-12-20 11:31:39 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:
Bug Depends On:	1502592
Bug Blocks:

Description Yedidyah Bar David 2017-10-17 14:27:04 UTC

Description of problem:

See also bug 1502592.

Comment 1 Yedidyah Bar David 2017-11-08 10:16:39 UTC

Clearing doc-text because we already say that users must upgrade to the next z-stream from the latest previous one. 4.1.7 is already out, so users of 4.2 will anyway have to upgrade to at least 4.1.7 when 4.2 is out.

Comment 2 Jiri Belka 2017-12-15 14:52:36 UTC

ok, as we recommend always from latest version inside $major.$minor (ie. 4.1.8 -> 4.2)

for archives, it failed from 4.1.6 -> 4.2 but 4.1.6 is not latest one per today:

from 4.1.6 to 4.2:

--> Processing Conflict: ovirt-engine-setup-plugin-ovirt-engine-4.2.0.2-0.1.el7.noarch conflicts ovirt-engine < 4.1.7
--> Finished Dependency Resolution
Error: ovirt-engine-setup-plugin-ovirt-engine conflicts with ovirt-engine-4.1.6.2-0.1.el7.noarch
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

4.1.6 -> 4.1.8 -> 4.2 worked ok - ovirt-engine-4.2.0.2-0.1.el7.noarch

Comment 3 Sandro Bonazzola 2017-12-20 11:31:39 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.