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 1762314 - Not enabling module deps when installing a pkg
Summary: Not enabling module deps when installing a pkg
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.0
Assignee: Jaroslav Mracek
QA Contact: Luca Berton
URL:
Whiteboard:
: 1783413 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 13:52 UTC by Michal Bocek
Modified: 2024-06-13 22:16 UTC (History)
6 users (show)

Fixed In Version: libdnf-0.38.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:48:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4678261 0 None None None 2022-06-24 13:00:39 UTC
Red Hat Product Errata RHBA-2020:1823 0 None None None 2020-04-28 16:48:54 UTC

Internal Links: 1783413

Description Michal Bocek 2019-10-16 13:52:32 UTC
Description of problem:
dnf does not enable all module stream dependencies during a pkg installation.

Version-Release number of selected component (if applicable):
dnf-0:4.2.7-6.el8.noarch

Steps to Reproduce:
1. Make sure perl and perl-YAML modules are not enabled
2. # dnf install perl-YAML
Installing:
 perl-YAML                 noarch               1.24-3.module+el8.1.0+2934+4e5567df   rhel-8-for-x86_64-appstream-rpms    93 k
Enabling module streams:
 perl-YAML                                      1.24
3. # dnf check
Modular dependency problem: Problem: conflicting requests
  - nothing provides module(perl:5.26) needed by module perl-YAML:1.24:8010020190322131811:a5949e2e-0.x86_64

Actual results:
During the perl-YAML installation dnf enabled only perl-YAML module causing a dependency problem described above in step 3.

Expected results:
dnf should have enabled also perl module which seems to be required by the perl-YAML module:
# dnf module enable perl-YAML
Enabling module streams:
 perl                        5.26                                                                                                          
 perl-YAML                   1.24

Comment 1 Jaroslav Mracek 2019-10-21 15:52:53 UTC
I create PR that resolves the issue: https://github.com/rpm-software-management/libdnf/pull/821
CI/gating tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/658

Comment 3 Michal Bocek 2019-10-30 14:08:32 UTC
Are you planning to release the fix also in 8.1.z?

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

Comment 10 Jaroslav Mracek 2022-06-24 13:00:39 UTC
*** Bug 1783413 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.