Description of problem: When locking a module it is not locked on the version of the installed profile but the latest available 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 --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 [root@2245f7e719eb /]# dnf module lock ModuleA Last metadata expiration check: 0:01:22 ago on Mon Oct 23 21:05:28 2017. 'ModuleA' is locked (stream: f26, version: 2) [root@2245f7e719eb /]# dnf module list --installed Last metadata expiration check: 0:01:26 ago on Mon Oct 23 21:05:28 2017. modularityABDE Name Stream Version Profiles ModuleA f26 2 [l] client, default [i], ... Hint: [d]efault, [i]nstalled, [l]ocked
Fixed by https://github.com/rpm-software-management/dnf/pull/969
The issue is solved by dnf-3.0.1-1 that was released into rawhide.