Bug 1497281

Summary: [modularity] dnf emits misleading errors if a module default stream cannot be found
Product: [Fedora] Fedora Reporter: Stephen Tweedie <sct>
Component: dnfAssignee: Martin Hatina <mhatina>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: dmach, jmracek, mhatina, rpm-software-management
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-04 11:05:11 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:

Description Stephen Tweedie 2017-09-29 15:54:18 UTC
Description of problem:
If a user runs "dnf install @module", and the module has no default stream (from the system profile), dnf ignores the module completely and complains that "Group '$module"' does not exist."

Version-Release number of selected component (if applicable):
dnf-2.6.5-1.git.102.e0caca2.fc27.noarch

How reproducible:
100%

Steps to Reproduce:
1. rm /etc/dnf/module.defaults.d/bikeshed.defaults 
  (or otherwise edit out the [httpd] system profile section)
2. dnf install @httpd

Actual results:
Loading repositories.
Last metadata expiration check: 0:00:00 ago on Fri 29 Sep 2017 03:46:24 PM UTC.
Warning: Group 'httpd' does not exist.
Error: Nothing to do.


Expected results:
Should return a more meaningful error about the module httpd: for example, maybe something like

Warning: Module 'httpd' has no default stream.
Streams available: 2.2, 2.4
Use "@httpd:2.2" or "@httpd:2.4" to select a stream.
Error: Nothing to do.

Comment 1 Martin Hatina 2017-10-04 11:05:11 UTC

*** This bug has been marked as a duplicate of bug 1497272 ***