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 1674562 - dnf not parsing default state of comps group correctly
Summary: dnf not parsing default state of comps group correctly
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Daniel Mach
QA Contact: BaseOS QE Security Team
Depends On: 1681084
TreeView+ depends on / blocked
Reported: 2019-02-11 16:13 UTC by Josh Boyer
Modified: 2020-11-14 10:55 UTC (History)
4 users (show)

Fixed In Version: dnf-4.2.7-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-05 22:21:12 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3583 0 None None None 2019-11-05 22:21:20 UTC

Description Josh Boyer 2019-02-11 16:13:33 UTC
Description of problem:

When attempting to have the anaconda Software Selection spoke display an "Add-on" for an environment selected by default (checked in the GUI), we ran into an issue where dnf/libcomps doesn't appear to return the right value for such a group.

anaconda is using the base dnf class to see if groups are set to default.  In a test compose, we have the headless-management group defined as:

  <name>Headless Management</name>
  <description> Tools for managing the system without an attached graphical console.
    <packagereq type="mandatory">cockpit-bridge</packagereq>
    <packagereq type="mandatory">cockpit-system</packagereq>
    <packagereq type="mandatory">cockpit-ws</packagereq>
    <packagereq type="mandatory">openssh-server</packagereq>

The group is also listed in the <optionlist> section of the environment.  When looking at the GUI, the headless management add-on is not selected, even though it should be.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Start an installation via anaconda, point it at a repo that has an addon with <default>true</default> defined
2. Go to the Software Spoke

Actual results:
add-on not selected by default

Expected results:
add-on selected by default

Additional info:

I've copied Martin Kolman from the anaconda team, who can help with how the anaconda code flow works as needed.

I also tried specifying <default>True</default> in case it was a case-sensitive issue, but it appears the compose tooling changed it back to "true" in the output comps.xml file.

Comment 8 errata-xmlrpc 2019-11-05 22:21:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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