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

Bug 1076046

Summary:	engine-setup fails on upgrade, tries to install ovirt-engine-setup instread of rhevm-setup
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yedidyah Bar David <didi>
Component:	ovirt-engine-setup	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Beňas <pbenas>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	aberezin, acathrow, alonbl, bazulay, cpelland, eedri, gklein, iheim, knesenko, pstehlik, Rhev-m-bugs, sbonazzo, scohen, yeylon, zdover
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	av5	Doc Type:	Bug Fix
Doc Text:	Due to changes in package branding, upstream defaults were used on the package upgrade availability check. This meant that the upgrade availability check failed causing engine-setup to exit due to missing ovirt-engine-setup package in the yum repository or channel. A first fix was introduced for fixing the package name branding, and then a second fix was needed to repair the yum group name branding. av3.1 has the first fix, allowing engine-setup to complete. However, it is missing the second fix, which is available only in av4. If you have only av3.1, you'll end up with some packages not updated to latest version after engine-setup runs (these include SDK packages and doc packages). As workaround, run "yum update". This updates all remaining packages updated to latest version.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1090946

Description Yedidyah Bar David 2014-03-13 12:33:16 UTC

Description of problem:

See summary.

This did not happen in 3.3 because there was a downstream-only patch to change the package name for which we check for updates. For 3.4 we want to make this cleaner.

Comment 1 Sandro Bonazzola 2014-03-17 14:37:30 UTC

The merged patch is incomplete: it takes care of the package name but it's missing package group name.

Comment 2 Alon Bar-Lev 2014-03-23 08:57:35 UTC

Hi Zac,

Just out of curiosity.

Why should we document a bug introduced at pre-release? Bugs that were not released into customers are part of release implementation, and are not exposed to users.

Thanks,

Comment 3 Yedidyah Bar David 2014-03-26 08:59:16 UTC

Moving back to post - still more fixes needed for version lock stuff to use the new env.

Comment 4 Petr Beňas 2014-03-28 17:52:20 UTC

Successfully updated to av5 using rhevm-setup-3.4.0-0.12.beta2.el6ev.noarch without any issues.

Comment 5 Zac Dover 2014-05-06 05:55:30 UTC

(In reply to Alon Bar-Lev from comment #2)
> Hi Zac,
> 
> Just out of curiosity.
> 
> Why should we document a bug introduced at pre-release? Bugs that were not
> released into customers are part of release implementation, and are not
> exposed to users.
> 
> Thanks,

Alon, 

This was one in a list of bugs that had docs text included. My pass through was an act of curation meant to clean up provided docs text.

I'll ping Chris Pelland and ask her if we need to document this one.

Zac

Comment 6 Zac Dover 2014-05-06 05:59:00 UTC

Chris,

Does this one need a release note?

Thanks in advance.

Zac

Comment 8 Itamar Heim 2014-06-12 14:08:40 UTC

Closing as part of 3.4.0