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 2058471 - dnf copr enable fails to pick epel-9 chroot
Summary: dnf copr enable fails to pick epel-9 chroot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dnf-plugins-core
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Copr Team
QA Contact: swm-qe
URL:
Whiteboard:
Depends On: 1994154
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 05:03 UTC by Carl George 🤠
Modified: 2022-11-15 13:01 UTC (History)
5 users (show)

Fixed In Version: dnf-plugins-core-4.1.0-2.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 11:15:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-113756 0 None None None 2022-02-25 05:04:42 UTC
Red Hat Product Errata RHBA-2022:8296 0 None None None 2022-11-15 11:15:30 UTC

Description Carl George 🤠 2022-02-25 05:03:01 UTC 
Description of problem:
When enabling a COPR repo on CentOS Stream 9, it fails to pick an available epel-9 chroot from the COPR repo [0].


Version-Release number of selected component (if applicable):
dnf-plugins-core-4.0.24-3.el9


Steps to Reproduce:
1. podman run -it --rm centos:stream9
2. dnf install 'dnf-command(copr)'
3. dnf copr enable @caddy/caddy


Actual results:
Error: This repository does not have any builds yet so you cannot enable it now.


Expected results:
Repository successfully enabled.


Additional info:
These same steps work on CentOS Stream 8 with dnf-plugins-core-4.0.21-10.el8.  I believe this is due to https://github.com/rpm-software-management/dnf-plugins-core/commit/9a00b1e405b421ae6c33c62f0442770fa6ba590e in 4.0.24, which I view as a regression.  I disagree with the rationale given in that commit message.  CentOS Stream is still Enterprise Linux and is EPEL compatible (with rare exceptions [1]).


[0] https://copr.fedorainfracloud.org/coprs/g/caddy/caddy/
[1] https://docs.fedoraproject.org/en-US/epel/epel-about-next/
Comment 1 Silvie Chlupova 2022-02-25 10:27:17 UTC 
Hi Carl,
you do not have centos-stream-9 enabled in your project. Once this commit https://github.com/rpm-software-management/dnf-plugins-core/commit/1a4dbdb35a7d4e791ebbdcd1a26af941a827cc77 will be in the new release you will see a better error message or if you visit the page https://copr.fedorainfracloud.org/coprs/g/caddy/caddy/repo/centos-stream-9/dnf.repo?arch=x86_64 you can see that the chroot doesn't exist in your project. You can still use:
dnf copr enable @caddy/caddy epel-9-x86_64
This will enable epel repo on your centos-stream. The same steps work on centos stream 8 because it uses dnf-plugins-core-4.0.21 and the change happened in dnf-plugins-core-4.0.24.
Comment 2 Carl George 🤠 2022-02-25 15:23:03 UTC 
There is no reason to have both the epel-9 and centos-stream-9 chroots enabled for the project.  CentOS Stream is EPEL compatible.  Furthermore, when COPR packages have dependencies from EPEL, the centos-stream-9 chroot is not usable.  When a COPR has an epel-9 chroot, and `dnf copr enable` is run on a CentOS Stream 9 system to enable that COPR, it should pick that chroot.
Comment 3 Carl George 🤠 2022-02-25 15:27:23 UTC 
Proposed fix.

https://gitlab.com/redhat/centos-stream/rpms/dnf-plugins-core/-/merge_requests/7
Comment 6 Jaroslav Mracek 2022-07-19 06:40:11 UTC 
The bug is fixed by a patch https://github.com/rpm-software-management/dnf-plugins-core/pull/459 that is already merged into upstream.
Comment 12 errata-xmlrpc 2022-11-15 11:15:26 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-plugins-core 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:8296
Note You need to log in before you can comment on or make changes to this bug.