Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-11024

Cannot ensure dnfmodule with no default profile

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 6.22.0, PUP 7.6.0
    • Component/s: None
    • Labels:
    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Story Points:
      1
    • Sprint:
      NW - 2021-04-14, NW-2021-04-28
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      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.
    • QA Risk Assessment:
      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

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              gabriel.nagy Gabriel Nagy
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support