Bug 743938

Summary:	Make rhev-hypervisor RPM multi-installable like the kernel
Product:	Red Hat Enterprise Linux 5	Reporter:	Perry Myers <pmyers>
Component:	rhev-hypervisor	Assignee:	Mike Burns <mburns>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.8	CC:	acathrow, apevec, cshao, djuran, kgrainge, leiwang, mburns, moli, ovirt-maint, sgordon, ycui, yeylon
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rhev-hypervisor-5.8-20111013.0.el5	Doc Type:	Bug Fix
Doc Text:	Previously, you could not run side-by-side installations of Red Hat Enterprise Virtualization Hypervisor. Now, side-by-side installations of the Hypervisor are facilitated by configuring yum to make rhev-hypervisor an install-only package. Edit the yum.conf file and add the installonlypkgs option: [main] ... installonlypkgs=rhev-hypervisor This option also needs to include the default list of install-only packages, which you can find by running the 'man yum.conf' command and searching for the installonlypkgs option.	Story Points:	---
Clone Of:	740565	Environment:
Last Closed:	2012-02-21 05:04:42 UTC	Type:	---
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:	740565
Bug Blocks:

Description Perry Myers 2011-10-06 14:21:48 UTC

+++ This bug was initially created as a clone of Bug #740565 +++

Description of problem:
Right now each install of RHEVH ISO overwrites the previous one.  We should make rhev-hypervisor install slotted so that each ISO is named like:

rhev-hypervisor-NVR.iso

and is placed in /usr/share/rhev-hypervisor

Then /usr/share/rhev-hypervisor/rhev-hypervisor.iso becomes symlink to last installed ISO

This will allow RHEVM to utilize the /usr/share/rhev-hypervisor directory directly as an ISO archive for their ISO uploader funtionality

Comment 3 Kate Grainger 2011-10-17 04:02:06 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, you could not run side-by-side installations of Red Hat Enterprise Virtualization Hypervisor. 

Now, you can allow side-by-side installations of the hypervisor by configuring yum to make rhev-hypervisor an install-only package. Edit the yum.conf file and add the installonlypkgs option:

[main]
...
installonlypkgs=rhev-hypervisor

This option also needs to include the default list of install-only packages, which you can find by running the man yum.conf command and looking at the installonlypkgs option.

Comment 5 Stephen Gordon 2012-02-10 15:15:33 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,9 +1,9 @@
 Previously, you could not run side-by-side installations of Red Hat Enterprise Virtualization Hypervisor. 
 
-Now, you can allow side-by-side installations of the hypervisor by configuring yum to make rhev-hypervisor an install-only package. Edit the yum.conf file and add the installonlypkgs option:
+Now, side-by-side installations of the Hypervisor are facilitated by configuring yum to make rhev-hypervisor an install-only package. Edit the yum.conf file and add the installonlypkgs option:
 
 [main]
 ...
 installonlypkgs=rhev-hypervisor
 
-This option also needs to include the default list of install-only packages, which you can find by running the man yum.conf command and looking at the installonlypkgs option.+This option also needs to include the default list of install-only packages, which you can find by running the 'man yum.conf' command and searching for the installonlypkgs option.

Comment 6 errata-xmlrpc 2012-02-21 05:04:42 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHSA-2012-0168.html