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

Bug 1409537

Summary:	ks-rhel-x86_64-server-6-6.7 kickstart pulls in 6.8 version of libxml2 (and more?) package
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Provisioning	Assignee:	Jiří Dostál <jdostal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Hutař <jhutar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	570	CC:	jdostal, tkasparek, tlestach
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-java-2.5.14-78-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-21 12:11:23 UTC	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:	1358815

Description Jan Hutař 2017-01-02 12:36:42 UTC

Description of problem:
ks-rhel-x86_64-server-6-6.7 kickstart pulls in 6.8 version of libxml2 (and more?) package


Version-Release number of selected component (if applicable):
spacewalk-java-2.3.8-158.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Create ks-rhel-x86_64-server-6-6.7 kickstart
2. Check version of libxml2 which is being installed there


Actual results:
6.8 version of the package is being installed


Expected results:
6.7 version of the package is being installed


Additional info:
I know that satellite does not know which version belongs to which RHEL release so it is hard, but possibly could be solved somehow.

Comment 2 Tomas Lestach 2017-01-02 14:06:12 UTC

I think this is expected behavior.
Satellite 5 uses specified kickstart tree to kickstart the system. However, later on 4 packages (pyOpenSSL, rhnlib, libxml2-python, libxml2) need to be installed and their latest versions are installed from the base channel to that the kickstarted system is to be registered. (There is not a good way to verify, whether they're part of the specified kickstart tree or not.)

I'd say it works as designed (more than 9) years ago. Not a regression and not a bug. Closing.

Comment 4 Jiří Dostál 2017-05-05 12:52:43 UTC

After an investigation I'm reopening this bug.
These packages were listed extra for historical reasons. We don't need to do that in RHEL5+, as they were intended for up2date (Although I have successfully made RHEL4 work *without* listing these packages. Just the version was different, but they must have had their purpose there. Can't verify without the original source code.) 

Let's force-install them only for RHEL4 and below
spacewalk.git e4f8defbeeb68d5d8435e4bed8c05f555ca7a9bd