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 1475781 - Optionally disable installation of platform-* and other unrequested packages
Summary: Optionally disable installation of platform-* and other unrequested packages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-27 10:40 UTC by Frantisek Kluknavsky
Modified: 2021-01-15 07:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:40:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frantisek Kluknavsky 2017-07-27 10:40:45 UTC
Description of problem:
Anaconda smartly installs a group platform-<autodetected_by_systemd>, which is often great and convenient but sometimes not wanted. For example, when installing a virtual machine to be later used as a container image, this is very damaging. Even explicitly listing the packages not to be installed like:
"""
%packages --excludedocs --instLangs=en --nocore --nobase 
-@platform-kvm
-qemu-guest-agent
"""
does not help. Packages are still installed against users explicit commands.

To spell it in the most general way, it would be nice to have a mechanism to defend against installing any package not explicitly requested.

Version-Release number of selected component (if applicable):
anaconda-21.48.22.121-1.el7

How reproducible:
deterministic

Steps to Reproduce:
1. kickstart with the snippet above
2. repo with a group "platform-kvm" containing "qemu-guest-agent" package
2. install in a kvm-based virtual machine

Actual results:
qemu-guest-agent installed

Expected results:
qemu-guest-agent not installed

Additional info:
platform-kvm group appeared with rhel 7.4

Comment 2 Frantisek Kluknavsky 2017-07-27 10:45:49 UTC
Feature originally discussed in https://bugzilla.redhat.com/show_bug.cgi?id=884385

Comment 3 Frantisek Kluknavsky 2017-07-27 10:46:51 UTC
Package group added in https://bugzilla.redhat.com/show_bug.cgi?id=1186734

Comment 4 Radek Vykydal 2017-07-27 12:49:04 UTC
The request makes sense to me.
We don't allow excluding packages or groups required by anaconda but I think adding option like --allow-removing-anaconda-requirements (but with some sane name) to %packages section would be an improvement.

Comment 6 RHEL Program Management 2021-01-15 07:40:20 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.