Bug 2064341

Summary: dnf group remove will not remove a group if repositories are disabled
Product: Red Hat Enterprise Linux 8 Reporter: Nicola Sella <nsella>
Component: dnfAssignee: Nicola Sella <nsella>
Status: CLOSED ERRATA QA Contact: Tomáš Bajer <tbajer>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.6CC: amatej, james.antill, mbanas, tbajer
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnf-4.7.0-9.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 10:47:20 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:
Embargoed:

Description Nicola Sella 2022-03-15 15:48:36 UTC
Description of problem:
dnf will not remove a group if the repository that contains the comps for that group is disabled.


Version-Release number of selected component (if applicable):
dnf-4.7.0-7.el8.noarch

Steps to Reproduce:
1. dnf group install Core
2. dnf group remove Core --disablerepo=*

Actual results:
Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".

Expected results:
Group gets removed

Additional info:
The bug is reproducible with any combination that excludes the repository from which the group is from such as --repo=<anyrepo> or --disablerepo=<group_repo>

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1927037

Comment 1 Nicola Sella 2022-03-15 15:57:58 UTC
fix: https://github.com/rpm-software-management/dnf/pull/1819

Comment 14 errata-xmlrpc 2022-11-08 10:47:20 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 (dnf bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2022:7712