Bug 1781769

Summary: Dnf does not correctly detect the latest version of the module stream
Product: Red Hat Enterprise Linux 8 Reporter: Marek Blaha <mblaha>
Component: dnfAssignee: Jaroslav Mracek <jmracek>
Status: CLOSED ERRATA QA Contact: Jan Blazek <jblazek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.2CC: dornelas, james.antill, kwalker, pkratoch, sct
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnf-4.2.17-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:49:06 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: 1186913, 1734579, 1779899    

Description Marek Blaha 2019-12-10 14:32:35 UTC
Description of problem:

The _get_latest() function of the module_base.py compares module versions as strings, but they are actually numbers. So at the moment the version 
820190206164045 is considered higher then 8010020190902091509.

Comment 1 Jaroslav Mracek 2019-12-11 11:21:41 UTC
I create a patch that fix detection of latest module (https://github.com/rpm-software-management/dnf/pull/1548)
Tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/728

Comment 4 David Darrah/Red Hat QE 2019-12-16 20:05:13 UTC
*** Bug 1779899 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2020-04-28 16:49:06 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