Bug 1709563

Summary:	yum operations on disabled appstreams should have more targeted error messages
Product:	Red Hat Enterprise Linux 8	Reporter:	Karl Abbott <kabbott>
Component:	yum	Assignee:	Jaroslav Mracek <jmracek>
Status:	CLOSED ERRATA	QA Contact:	Radek Bíba <rbiba>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	amatej, james.antill, mkyral
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	dnf-4.2.17-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:47:49 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:
Bug Depends On:
Bug Blocks:	1649352

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