Jira (PUP-11200) Allow loading from scripts mount when loading Task files
Title: Message Title Josh Cooper commented on PUP-11200 Re: Allow loading from scripts mount when loading Task files Merged to 6.x in https://github.com/puppetlabs/puppet/commit/a64d9e31537843bbc20cf824a986c7829d8b9644 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410089.1628201512000.102635.1628294040045%40Atlassian.JIRA.
Jira (PUP-11200) Allow loading from scripts mount when loading Task files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11200 Allow loading from scripts mount when loading Task files Change By: Josh Cooper Fix Version/s: PUP 7.10.0 Fix Version/s: PUP 6.25.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410089.1628201512000.102636.1628294040105%40Atlassian.JIRA.
Jira (PUP-11203) puppet module upgrade often reports the wrong module when resolving dependency issues
Title: Message Title
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-nodejsError: Could not upgrade module 'puppet-nodejs' (v7.0.1 -> latest) There are 3 newer versionsNo combination of dependency upgrades would satisfy all dependenciesDependencies will not be automatically upgraded across major versionsUpgrading one or more of these modules may permit the upgrade to succeed:- puppetlabs-stdlibUse `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
Jira (PUP-11203) puppet module upgrade often reports the wrong module when resolving dependency issues
Title: Message Title 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 This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410754.1628283761000.102446.1628283840045%40Atlassian.JIRA.
Jira (PUP-11203) puppet module upgrade often reports the wrong module when resolving dependency issues
Title: Message Title
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-nodejsError: Could not upgrade module 'puppet-nodejs' (v7.0.1 -> latest) There are 3 newer versionsNo combination of dependency upgrades would satisfy all dependenciesDependencies will not be automatically upgraded across major versionsUpgrading one or more of these modules may permit the upgrade to succeed:- puppetlabs-stdlibUse `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
Jira (PUP-11203) puppet module upgrade often reports the wrong module when resolving dependency issues
Title: Message Title 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
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title
Ciprian Badescu updated an issue
Puppet / PUP-11201
Refine when the last used environment is used
Change By:
Ciprian Badescu
With the recent changes in PUP-10216, the agent stores the last used environment in {{last_run_summary.yaml}}. If the next run does not specify an environment on the CLI, then the last used environment *always* takes precedence over the environment specified in puppet.conf. For example, given:{noformat}# puppet agent -t --environment feature_branch# puppet agent -t{noformat}If the agent is allowed to specify its environment:Prior to PUP-10216, the second run would use the original configured environment from puppet.conf or default to "production".After PUP-10216, the second run uses the "feature_branch" environment. This is also true if the second run occurs in the background (systemd/cron), which is especially surprising.In cases where the agent is *not* allowed to specify its environment, the last used environment provides the same function that the node request did. So the agent's behavior before and after PUP-10216 is the same, assuming the agent pluginsync'ed the right set of facts and classification doesn't change between runs.This ticket proposes we make an exception for the agent-specified case so that the second run only uses the environment from the previous run if it was server-specified. Otherwise, the agent should start in its configured environment (from puppet.conf) or default to "production".So I think this means: # If environment specified on CLI, use it# If last environment was server-specified, use it# Otherwise use our configured environment {{Puppet[:environment]}}I think we can detect if the last environment was server-specified by saving both the initial environment and the converged environment in {{last_run_summary . yaml}}. If those are different, then the server told us to use a different environment.If they are the same, then it doesn't matter if it's agent or server-specified, just use it.
Add Comment
Jira (PUP-11202) managehome=true on Windows fails
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11202
managehome=true on Windows fails
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/06 6:38 AM
Priority:
Normal
Reporter:
Luchian Nemes
Docs state support for the managehome parameter of user resource on Windows but it does not seem to work, as seen below:
> puppet resource user 'test' ensure=present
Notice: /User[test]/ensure: created
user { 'test':
ensure => 'present',
provider => 'windows_adsi',
}
Jira (PUP-11200) Allow loading from scripts mount when loading Task files
Title: Message Title Lucy Wyman updated an issue Puppet / PUP-11200 Allow loading from scripts mount when loading Task files Change By: Lucy Wyman Release Notes: Bug Fix Release Notes Summary: Allow tasks to load files from the scripts mount. Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410089.1628201512000.101123.1628255040032%40Atlassian.JIRA.
Jira (PDB-5213) Update PDB to pick up i18n changes from clj-parent
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici PuppetDB / PDB-5213 Update PDB to pick up i18n changes from clj-parent Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408750.1627457775000.101037.1628246160038%40Atlassian.JIRA.
