Description of problem: When having module profile version installed older than the latest the module listing is confusing as the installed profile is not listed by default but the latest one. See below. Version-Release number of selected component (if applicable): dnf-2.7.5-4.fc26.modularity.1.3fb9e5c.git.8052.52e0d41None.noarch [root@2245f7e719eb /]# dnf module install ModuleA:f26:1/default Last metadata expiration check: 0:00:27 ago on Mon Oct 23 21:05:28 2017. Dependencies resolved. ... ... Complete! [root@2245f7e719eb /]# dnf module list Last metadata expiration check: 0:00:35 ago on Mon Oct 23 21:05:28 2017. modularityABDE Name Stream Version Profiles ModuleA f26 2 client, default, ... ModuleB f26 2 default ModuleD f26 1 default ModuleE f26 1 default Hint: [d]efault, [i]nstalled, [l]ocked [root@2245f7e719eb /]# dnf module list --installed Last metadata expiration check: 0:00:41 ago on Mon Oct 23 21:05:28 2017. modularityABDE Name Stream Version Profiles ModuleA f26 1 client, default [i], ... Hint: [d]efault, [i]nstalled, [l]ocked Compare the output to the package listing. [root@2245f7e719eb /]# dnf list TestA Last metadata expiration check: 0:00:47 ago on Mon Oct 23 21:05:28 2017. Installed Packages TestA.noarch 1-1.modA @modularityABDE Available Packages TestA.noarch 1-2.modA modularityABDE [root@2245f7e719eb /]#
Fixed by https://github.com/rpm-software-management/dnf/pull/971