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 1709563 - yum operations on disabled appstreams should have more targeted error messages
Summary: yum operations on disabled appstreams should have more targeted error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: yum
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Jaroslav Mracek
QA Contact: Radek Bíba
URL:
Whiteboard:
: 1638024 (view as bug list)
Depends On:
Blocks: 1649352
TreeView+ depends on / blocked
 
Reported: 2019-05-13 20:10 UTC by Karl Abbott
Modified: 2021-02-16 13:48 UTC (History)
3 users (show)

Fixed In Version: dnf-4.2.17-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:47:49 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1823 0 None None None 2020-04-28 16:48:03 UTC

Description Karl Abbott 2019-05-13 20:10:25 UTC 
Description of problem:

Currently, when trying to install a package from a disabled application stream, yum reports that it cannot find a match. This may cause confusion and cause people to troubleshoot why they cannot install said package. The error message should be more targeted to provide the end user with a better understanding of why they cannot install the package.

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

yum-4.0.9.2-5.el8.noarch

How reproducible:

Always

Steps to Reproduce:
1. yum module disable mariadb 
2. yum install mariadb -y
3.

Actual results:

Updating Subscription Management repositories.
Last metadata expiration check: 0:00:28 ago on Mon 13 May 2019 04:03:58 PM EDT.
No match for argument: mariadb
Error: Unable to find a match

Expected results:

Updating Subscription Management repositories.
Last metadata expiration check: 0:00:28 ago on Mon 13 May 2019 04:03:58 PM EDT.
The application stream that mariadb belongs to has been disabled on this host.

Additional info:
Comment 1 Jaroslav Mracek 2019-11-01 12:21:00 UTC 
Thanks for the report. With modular filtering we have not a direct approach how to easily identify where and why package was excluded. Also your request could have multiple solutions therefore the error message cannot be very detailed. I am supposing to add following messages:


All matches were excluded by regular and modular filtering for argument: mariadb
All matches were excluded by regular filtering for argument: mariadb
All matches were excluded by modular filtering for argument: mariadb
Argument matched only with source RPMs: mariadb

Also I will create a chapter in man-pages where I will explain what is modular and regular filtering and how to investigate your problem.

Please could you verify that proposed solution is resolving the report?
Comment 2 Jaroslav Mracek 2019-11-04 08:42:14 UTC 
The patch is available here: https://github.com/rpm-software-management/dnf/pull/1518
Comment 3 Jaroslav Mracek 2019-11-13 14:05:01 UTC 
The solution is related to https://github.com/rpm-software-management/libdnf/pull/840.
Comment 4 Jaroslav Mracek 2019-11-22 08:03:36 UTC 
*** Bug 1638024 has been marked as a duplicate of this bug. ***
Comment 5 Karl Abbott 2019-11-25 12:53:24 UTC 
I believe that the proposed solution will be sufficient in this case. Thanks for your work here!

Cheers,
Karl
Comment 10 errata-xmlrpc 2020-04-28 16:47:49 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
Note You need to log in before you can comment on or make changes to this bug.