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

puppet module upgrade often reports the wrong module when resolving dependency issues



    • Bug
    • Status: Accepted
    • Normal
    • Resolution: Unresolved
    • None
    • None
    • Modules
    • None
    • Needs Assessment


      Puppet Version: 6.23
      Puppet Server Version: 6.16
      OS Name/Version: Any

      In a lot of cases, when running a puppet module upgrade if there are dependency issues, the wrong module is recommended. This forces the admin to need to grep through module metadata.json files to find the correct one

      Desired Behavior:
      Puppet should better detect which module is failing dependencies

      Actual Behavior:


      Example: Upgrading puppet-nodejs from version 7.0.1 to latest with puppetlabs-stdlib 6.6.0 and wazuh-wazuh 4.0.4 installed


      puppet module upgrade puppet-nodejs
      Error: Could not upgrade module 'puppet-nodejs' (v7.0.1 -> latest)
        There are 3 newer versions
          No combination of dependency upgrades would satisfy all dependencies
          Dependencies will not be automatically upgraded across major versions
          Upgrading one or more of these modules may permit the upgrade to succeed:
          - puppetlabs-stdlib
          Use `puppet module upgrade --force` to upgrade only this module

      Puppet recommends updating puppetlabs-stdlib however version 6.6.0 satisfies the dependency requirement on Forge for nodejs (puppetlabs/stdlib (>= 4.25.0 < 8.0.0))


      After grepping which modules contains nodejs, it is found that the wazuh module's manifest has nodejs as a dependency with version >= 3.0.0 < 8.0.0 specified. Puppet should be able to determine this on its own.



        Issue Links



              Unassigned Unassigned
              mluck94 Michael Luck
              0 Vote for this issue
              2 Start watching this issue



                Zendesk Support