Bug 1674562

Summary: dnf not parsing default state of comps group correctly
Product: Red Hat Enterprise Linux 8 Reporter: Josh Boyer <jwboyer>
Component: dnfAssignee: Daniel Mach <dmach>
Status: CLOSED ERRATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: low    
Version: 8.0CC: dmach, james.antill, mblaha, mkolman
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: dnf-4.2.7-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:21:12 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:
Bug Depends On: Red Hat1681084    
Bug Blocks:    

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.