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 2072441 - repomanage --new seems to exclude currently enabled modules
Summary: repomanage --new seems to exclude currently enabled modules
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf-plugins-core
Version: 8.5
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: amatej
QA Contact: Eva Mrakova
Mariya Pershina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-06 10:28 UTC by Francois Andrieu
Modified: 2022-11-08 12:46 UTC (History)
4 users (show)

Fixed In Version: dnf-plugins-core-4.0.21-12.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 10:53:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-118033 0 None None None 2022-04-06 10:39:33 UTC
Red Hat Product Errata RHBA-2022:7759 0 None None None 2022-11-08 10:53:23 UTC

Description Francois Andrieu 2022-04-06 10:28:22 UTC
Description of problem:
repomanage --new doesn't always list newest stream version of currently enabled modules.


Version-Release number of selected component (if applicable):
dnf-plugins-core-4.0.21-4.el8_5


How reproducible:
Always

Steps to Reproduce:
On RHEL 8.5:
1. Sync the appstream repo from an older version
  $ dnf --releasever=8.3 reposync --norepopath -p /tmp/8.3 --downloadcomps --download-metadata --repo=rhel-8-for-x86_64-appstream-rpms
2. Enable any module (ie. python36)
  $ dnf module -y enable python36
3. List newest packages in this repo
  $ repomanage -n /tmp/8.3 | grep python36
 

Actual results:
~~~
$ dnf module -y enable python36
Updating Subscription Management repositories.
Last metadata expiration check: 0:48:59 ago on Wed Apr  6 11:25:54 2022.
Dependencies resolved.
=================================================================================================================
 Package                   Architecture             Version                      Repository                 Size
=================================================================================================================
Enabling module streams:
 python36                                           3.6                                                         

Transaction Summary
=================================================================================================================

Complete!

$ repomanage -n /tmp/8.3 | grep python36
Added repomanage_repo repo from /tmp/8.3
<no result>

$ dnf module -y disable python36
Updating Subscription Management repositories.
Last metadata expiration check: 0:49:46 ago on Wed Apr  6 11:25:54 2022.
Dependencies resolved.
=================================================================================================================
 Package                   Architecture             Version                      Repository                 Size
=================================================================================================================
Disabling modules:
 python36                                                                                                       

Transaction Summary
=================================================================================================================

Complete!

$ repomanage -n /tmp/8.3 | grep python36
Added repomanage_repo repo from /tmp/8.3
/tmp/8.3/Packages/p/python36-3.6.8-2.module+el8.1.0+3334+5cb623d7.x86_64.rpm
/tmp/8.3/Packages/p/python36-debug-3.6.8-2.module+el8.1.0+3334+5cb623d7.x86_64.rpm
/tmp/8.3/Packages/p/python36-devel-3.6.8-2.module+el8.1.0+3334+5cb623d7.x86_64.rpm
/tmp/8.3/Packages/p/python36-rpm-macros-3.6.8-2.module+el8.1.0+3334+5cb623d7.noarch.rpm

~~~

Expected results:
repomanage should list the newest module stream in the target repository, regardless of the state of the modules on the running system.

Additional info:

Comment 9 errata-xmlrpc 2022-11-08 10:53:15 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 (dnf-plugins-core bug fix and enhancement update), 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-2022:7759


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