Bug 182090

Summary:	Config Channel is not being deployed to a RHEL-4-WS update 2 client.
Product:	Red Hat Satellite 5	Reporter:	Dominik Schmid <dominik.schmid>
Component:	Configuration Management	Assignee:	Todd Sanders <tsanders>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	cperry
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:	2009-08-22 02:33:51 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:

Description Dominik Schmid 2006-02-20 12:45:10 UTC

Description of problem:
Config Channel is not being deployed to the client at postinstallation.

Version-Release number of selected component (if applicable):
The client (server to set up with kickstarting) is RHEL-4-WS Update 2.
RHN Server 3.6.6

How reproducible:
Make a kickstartfile for a client with rhel 4 update 2, add few files to the
applied config channel and kickstart the server.
The files are not going to be deployed in the post-installation section.

Actual results:
RHEL-4-WS update 1 works well.
I don't know if this failure exists in newer releases of rhn-server.

Expected results:


Additional info:

Comment 1 Red Hat Bugzilla 2007-05-03 05:38:45 UTC

User wregglej's account has been closed

Comment 3 Clifford Perry 2009-08-22 02:33:51 UTC

Satellite 3.x has EOL'd. Closing this bug out. 

http://www.redhat.com/security/updates/satellite/

Regards,
Cliff