Bug 206497

Summary:	the ShadowActions that install rhn-virtualization-host and rhn-virtualization-guest should use virtual provides
Product:	Red Hat Satellite 5	Reporter:	John Wregglesworth <wregglej>
Component:	Other	Assignee:	Todd Sanders <tsanders>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-05 22:50:32 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:
Bug Blocks:	462714

Description John Wregglesworth 2006-09-14 18:39:37 UTC

Description of problem: The ShadowActions that schedule the install of
rhn-virtualization-host and rhn-virtualization-guest currently grab package
information based on their name. We need to change this so that they grab
package information using a virtual provides, that way we can change the name of
the packages if we need to.

Comment 1 Red Hat Bugzilla 2007-05-03 05:41:19 UTC

User wregglej's account has been closed

Comment 3 Clifford Perry 2011-01-05 22:50:32 UTC

The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of
life. Please see:

Satellite 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0001.html

RHN Proxy 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0002.html

This bugzilla was reported for an unspecified version of the product, but was created prior to the release of 5.x - as such we assume this bug was reported for the 4.x version of the product - which is no longer supported. 

https://access.redhat.com/support/policy/updates/satellite/
RHN Satellite and Proxy Server 5
General availability: 	June 26, 2007

We are closing this bugzilla out. If you feel this bug report should be
reviewed again since it is valid for a currently supported product version,
then please feel free to re-open this bug report. 

Regards,
Clifford