RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1246367 - Documentation describes use of --nobase with %packages in kickstart, but ksvalidator says --nobase is deprecated and has no effect
Summary: Documentation describes use of --nobase with %packages in kickstart, but ksva...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Installation_Guide
Version: 7.1
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Clayton Spicer
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-24 06:11 UTC by Joe Thompson
Modified: 2019-03-06 02:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-10 19:52:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Package differance between @core and --nobase installation. (12.21 KB, application/vnd.oasis.opendocument.spreadsheet)
2015-10-08 10:19 UTC, Johan Bergström 		no flags Details
View All

Description Joe Thompson 2015-07-24 06:11:47 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-packages

Section Number and Name: 23.3.3. Package Selection

Describe the issue: Documentation describes --nobase as follows: "Do not install the @Base group. Use this option to perform a minimal installation, for example, for a single-purpose server or desktop appliance."

However, when parsing a kickstart that includes --nobase, ksvalidator outputs:

"The --nobase option has been deprecated and no longer has any effect.  It may be removed from future releases, which will result in a fatal error from kickstart.  Please modify your kickstart file to remove this option."

Suggestions for improvement: If --nobase in fact deprecated and has no effect, as appears to be the case, update the documentation to suit; otherwise patch ksvalidator not to state this in output.
Comment 4 Johan Bergström 2015-10-08 10:17:45 UTC 
It is still honoring --nobase even tho ksvalidator complains about it.

We just tested, a @core (and @base it was the same) installation has 488 RPM packages installed.

Using --nobase it will install 324 RPM packages.

We were planning to use --nobase for a smaller installation footprint. Is there any specific reason why you are moving away from it ? Is there any good alternative to make a minimal server installation?
Comment 5 Johan Bergström 2015-10-08 10:19:42 UTC 
Created attachment 1080962 [details]
Package differance between @core and --nobase installation.
Comment 6 Petr Bokoc 2016-01-20 12:46:32 UTC 
Alright, we'll investigate further.
Comment 7 Clayton Spicer 2016-04-20 18:25:01 UTC 
Hi Johan,
Could you possibly send us the kickstart file used to generate the above attachment?
Comment 8 Johan Bergström 2016-04-25 06:49:50 UTC 
I don't have that specific kickstart file anymore, but as I remember, it was a very simple test between running the packageselection @core versus @core --nobase base on RHEL7.1

That's pretty much it.
Comment 13 Clayton Spicer 2016-05-17 18:54:43 UTC 
According to our engineering department, simply installing the packages in the @core group (which are installed by default) will result in a minimal working system. It is possible to disable installation of these packages with the --nocore option, but then you must ensure that all necessary packages are included in the %packages section of your kickstart file.

Unfortunately, it seems that we do need the kickstart files to be able to say what exactly was causing the difference you reported in the quantity of installed packages. However if you can find the file and reproduce the situation, I would certainly recommend filing a bug report against the installation software - you can do so by going to https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%207 and select 'anaconda' in the component drop-down.
Comment 16 Petr Bokoc 2017-04-10 19:52:04 UTC 
Released: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-packages
Comment 17 Om Prakash Singh 2018-04-03 11:59:30 UTC 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-installing_the_minimum_amount_of_packages_required

and


https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Security_Guide/Red_Hat_Enterprise_Linux-7-Security_Guide-en-US.pdf


still contains --nobase as option.
Note You need to log in before you can comment on or make changes to this bug.