Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
# cat /etc/yum.repos.d/bz1151154repo*
[bz1151154repoA]
name=My Local Repo bz1151154repoA
baseurl=file:///tmp/tmp.7fxA6gpJvW/bz1151154repoA/
enabled=0
gpgcheck=0
[bz1151154repoB]
name=My Local Repo bz1151154repoB
baseurl=file:///tmp/tmp.7fxA6gpJvW/bz1151154repoB/
enabled=0
gpgcheck=0
# yum-config-manager --enable
Updating Subscription Management repositories.
Unable to read consumer identity
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Error: Trying to enable already enabled repos.
# cat /etc/yum.repos.d/bz1151154repo*
[bz1151154repoA]
name=My Local Repo bz1151154repoA
baseurl=file:///tmp/tmp.kESYbvMVMs/bz1151154repoA/
enabled=0
gpgcheck=0
[bz1151154repoB]
name=My Local Repo bz1151154repoB
baseurl=file:///tmp/tmp.kESYbvMVMs/bz1151154repoB/
enabled=0
gpgcheck=0
# rpm -q dnf-utils
dnf-utils-4.0.2.2-3.el8.noarch
Comment 1Pavla Kratochvilova
2019-09-23 11:03:07 UTC
Karel, can you please clarify, what did you mean by "ambiguous" in the summary? I think the message is not ambiguous, but plainly wrong, because dnf is not trying to enable any repository.
If the above is correct, I propose the following acceptance criteria:
AC: "yum-config-manager --enable" without arguments outputs the same as "yum-config-manager --disable", i.e. empty stderr and stdout.
Hi,
I was complaining on the message "Error: Trying to enable already enabled repos." while not having any repository enabled.
How much is running "yum-config-manager --enable" correct? You AC is probably sane assuming the RFE 1706384 won't be implemented.
Comment 3Pavla Kratochvilova
2019-09-24 17:19:43 UTC
> I was complaining on the message "Error: Trying to enable already enabled repos." while not having any repository enabled.
All right, thanks.
> How much is running "yum-config-manager --enable" correct?
The old yum-config-manager exited with 0 when run with "--enable" without other arguments, so I wouldn't change that.
Comment 6Pavla Kratochvilova
2020-01-03 13:25:30 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.
https://access.redhat.com/errata/RHBA-2020:1823