Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Night's Watch
-
1
-
NW - 2021-04-14, NW - 2021-04-28
-
Needs Assessment
-
Bug Fix
-
This release fixes an issue where using the dnfmodule provider to install a module with no default profile without passing the `enable_only` parameter would fail with newer versions of DNF.
-
Needs Assessment
Description
OS Name/Version: CentOS/RedHat 8
When we added the enable functionality to the dnfmodule provider, we made the following statement: DNF modules that have no default profile (and cannot be installed) will be enabled by default, so there is no need to add enable_only.
However this does not work anymore with the latest versions of DNF (at least 4.2.23).
Attempting to apply a resource like the following will fail, requiring the user to also add enable_only:
package { '389-ds': ensure => present, provider => dnfmodule }
|
Desired Behavior:
Puppet should enable the module
Actual Behavior:
Execution fails and an error message is raised
Attachments
Issue Links
- relates to
-
PUP-10235 Support enable module with dnfmodule package provider
-
- Resolved
-