Bug 1748841 - dnf: Bad id for repo when dnf variables are used inside repoid field of repo file
Summary: dnf: Bad id for repo when dnf variables are used inside repoid field of repo ...
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: Jaroslav Rohel
QA Contact: Jan Blazek
Depends On:
TreeView+ depends on / blocked
Reported: 2019-09-04 09:30 UTC by Manu
Modified: 2020-04-28 16:48 UTC (History)
2 users (show)

Fixed In Version: dnf-4.2.17-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-04-28 16:48:13 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4620111 0 None None None 2019-11-28 20:05:57 UTC
Red Hat Product Errata RHBA-2020:1823 0 None None None 2020-04-28 16:48:54 UTC

Description Manu 2019-09-04 09:30:46 UTC
Description of problem:

When dnf variables are used inside the repoid field of repo file, the following error is thrown. 

	Bad id for repo: testa-$basearch-$releasever, byte = $ 5

The dnf variables are working fine on other fields of the repo file.

This has been reproduced on both RHEL 8 and Fedora 30

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


Steps to Reproduce:

1.Create a repo file with dnf variables in the repoid field
2.Run # dnf repolist

Actual results:

Bad id for repo: testa-$basearch-$releasever, byte = $ 5

Expected results:

The variables should be resolved to their values.

Additional info:

Repo files on RHEL 7 and RHEL 8 has no issue with usage of yum variables inside the repoid field

Comment 2 Jaroslav Rohel 2019-11-21 11:20:31 UTC
PR: https://github.com/rpm-software-management/dnf/pull/1537

Comment 7 errata-xmlrpc 2020-04-28 16:48:13 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.