Bug 1318795

Summary:	KS parameter "nobase" is not already supported in Fedora22
Product:	[Community] Spacewalk	Reporter:	Martin Korbel <mkorbel>
Component:	Server	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.4	CC:	jdobes
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-21 13:12:10 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:

Description Martin Korbel 2016-03-17 20:37:38 UTC

Description of problem:
Kickstart option "nobase" is not already supported in F22 or newer. 
Look at https://docs.fedoraproject.org/en-US/Fedora/22/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html#sect-installation > 3.2.4 Changes in Kickstart Syntax > first paragraph.


Version-Release number of selected component (if applicable):
SW2.5 nightly

How reproducible:
100%

Steps to Reproduce:
1. Create new KS profile for Fedora 22 or 23
2. Open page "Install Packages by Package Name and Group" (https://<fqdn>/rhn/kickstart/KickstartPackagesEdit.do?ksid=1)
3. insert name of some package (ex. vim-enhanced) and press "Update packages"
4. SW automatically adds a package group "@ Base", but this group does not exist in Fedora.
5. we can check the "Don't install @Base package group:" checkbox and press "Update packages"
6. open page "Kickstart file" (https://<fqdn>/rhn/kickstart/KickstartFileDownload.do?ksid=1) 


Actual results:
%packages  --nobase
vim-enhanced
perl
wget
rhn-setup
rhn-check
rhn-client-tools
%end


Expected results:
%packages
vim-enhanced
perl
wget
rhn-setup
rhn-check
rhn-client-tools
%end


Additional info:

Comment 1 Michael Mráka 2019-10-21 13:12:10 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.