Jira (PUP-11203) puppet module upgrade often reports the wrong module when resolving dependency issues

[Michael Luck (Jira)]

Michael Luck created an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues Issue Type: Bug Assignee: Unassigned Components: Modules Created: 2021/08/06 2:02 PM Priority: Normal Reporter: Michael Luck 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 manifests 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. Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

[Michael Luck (Jira)]

Michael Luck updated an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues

Change By: Michael Luck *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 manifests 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

{code:java}

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

{code} Puppet recommends updating puppetlabs-stdlib however version 6.6.0 satisfies the dependency requirement on Forge for nodejs ([puppetlabs/stdlib|https://forge.puppet.com/modules/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.

!image-2021-08-06-17-03-48-841.png!

Puppet should be able to determine this on its own.

Add Comment

[Michael Luck (Jira)]

Michael Luck updated an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues

Change By: Michael Luck Attachment: image-2021-08-06-17-03-48-841.png

Add Comment

[Michael Luck (Jira)]

Michael Luck updated an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues Change By: Michael Luck

*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 manifests 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   {code:java}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 {code} Puppet recommends updating puppetlabs-stdlib however version 6.6.0 satisfies the dependency requirement on Forge for nodejs ([puppetlabs/stdlib|https://forge.puppet.com/modules/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. !image-2021-08-06-17-03-48-841.png!

Puppet should be able to determine this on its own.

Add Comment

[Michael Luck (Jira)]

Michael Luck updated an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues Change By: Michael Luck

*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 manifests 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   {code:java}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 {code} Puppet recommends updating puppetlabs-stdlib however version 6.6.0 satisfies the dependency requirement on Forge for nodejs ([puppetlabs/stdlib|https://forge.puppet.com/modules/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. !image-2021-08-06-17-03-48-841.png!

Add Comment

[Ciprian Badescu (Jira)]

Ciprian Badescu updated an issue

Puppet / PUP-11203 puppet module upgrade often reports the wrong module when resolving dependency issues

Change By: Ciprian Badescu Epic Link: PUP-11215

Add Comment