Hi, trying to solve issue with dsc_storage on windows with a failover cluster. Once the cluster is configured, there are references to disks from the node that the first node is clustered with which do not have disk numbers, resulting in "Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.UInt64"" errors causing the agent to record a failed agent run. Has anyone seen this or similar? Insight is greatly appreciated, thank you.

This message was deleted.

Hi, i have some questions about the pltraining-rbac module: I am trying to manage user passwords and have the following behaviour: • If I create a new user, I am able to set a password • If I have an existing user, the password will not be updated/set. I had a look at the provider, and found this piece of code: https://github.com/puppetlabs/pltraining-rbac/blob/master/lib/puppet/provider/rbac_user/ruby.rb#L86 This seems to indicate, the module is not able to manage the password at all. But on the other hand it seems this password method is never used. Is it safe to remove it? The set_password method seems to be the place where all the logic happens: https://github.com/puppetlabs/pltraining-rbac/blob/master/lib/puppet/provider/rbac_user/ruby.rb#L134 I understood the method does the following: It takes the user ID and the desired password as arguments and checks if the ID is a string and confirms if the user exists, otherwise it throws an error. Afterwards the provider calls the API to receive a password reset token and creates the payload for the Password reset request and performs the API call to reset the password. • for me it looks like, the password reset is performed always as long as the user provides a password parameter. Is that correct? • Why is a password not updated for an existing user? It should be possible to check a users password using the

POST /command/validate-password

endpoint, and to update the password only in case the password provided is not matching the existing. I also need to generate tokens, is this a valuable addition to the module?

Hi, i have some questions about the pltraining-rbac module: I am trying to manage user passwords and have the following behaviour: • If I create a new user, I am able to set a password • If I have an existing user, the password will not be updated/set. I had a look at the provider, and found this piece of code: https://github.com/puppetlabs/pltraining-rbac/blob/master/lib/puppet/provider/rbac_user/ruby.rb#L86 This seems to indicate, the module is not able to manage the password at all. But on the other hand it seems this password method is never used. Is it safe to remove it? The set_password method seems to be the place where all the logic happens: https://github.com/puppetlabs/pltraining-rbac/blob/master/lib/puppet/provider/rbac_user/ruby.rb#L134 I understood the method does the following: It takes the user ID and the desired password as arguments and checks if the ID is a string and confirms if the user exists, otherwise it throws an error. Afterwards the provider calls the API to receive a password reset token and creates the payload for the Password reset request and performs the API call to reset the password. • for me it looks like, the password reset is performed always as long as the user provides a password parameter. Is that correct? • Why is a password not updated for an existing user? It should be possible to check a users password using the

POST /command/validate-password

endpoint, and to update the password only in case the password provided is not matching the existing. I also need to generate tokens, is this a valuable addition to the module?

I managed to use Puppet Enterprise to install updates on an Ubuntu Linux system. But I have also a Ubuntu Linux system with a MySQL-server. On this system beside other also MySQL-server updates are available. Because the MySQL-server is in use, all updates may be installed except the MYSQL server updates. The MySQL-server updates should be installed later. How to define which updates can be installed? In PATH MANAGEMENT/Patches, I see "Patch groups"? Should I use "Patch groups"? Where can I define "Patch groups"?

I believe the patch groups are configured via the pe_patch module. https://www.puppet.com/docs/pe/2021.1/patch_management_setup.html Per that documentation, you'll want to use apt-mark to flag the mysql packages so they aren't patched.

After running a Puppet job, I get the message: "Job finished with failures. See node run results for details". I see also "Job node status" "Failed - erro..." Where can I find the "node run results" (with details) ?

After running a Puppet job, I get the message: "Job finished with failures. See node run results for details". I see also "Job node status" "Failed - erro..." Where can I find the "node run results" (with details) ?

I'd look on the Orchestration -> Tasks or Enforcement->Jobs

Just a reminder those wanting to know about how Puppet 8 will affect things https://github.com/puppetlabs/puppet/wiki/Puppet-8-Compatibility Puppet 8 will appear in PE 2023 in an upcoming minor release

This message was deleted.

This message was deleted.

Can someone from Puppet please check https://github.com/puppetlabs/pe_patch/issues/91 and https://github.com/puppetlabs/pe_patch/pull/92

Supported modules released puppet-lint 3.3.0 has been released What it is: Puppet Lint tests Puppet code against the recommended Puppet language style guide. Where you can find it: - https://rubygems.org/gems/puppet-lint - Release notes: https://github.com/puppetlabs/puppet-lint/blob/main/CHANGELOG.md Key features/changes: - Fixed

Corrects legacy macOS fact interpretation issues corrected in https://github.com/puppetlabs/puppet-lint/pull/103 by https://github.com/mhashizume

Feedback: - https://github.com/puppetlabs/puppet-lint/issues puppetlabs-wsus_client 5.0.0 has been released What it is: wsus_client is a module used to Manage WSUS (Windows Server Update Service) settings for client nodes Where you can find it: - https://forge.puppet.com/modules/puppetlabs/wsus_client/readme - https://github.com/puppetlabs/puppetlabs-wsus_client/blob/main/CHANGELOG.md Key features/changes: - Added

Support for Windows 2022

- Changed

Dropped support for windows 7, 8, 2008 Server and 2008 Server R2

Set parameters of module to use data types

Feedback: - https://github.com/puppetlabs/puppetlabs-wsus_client/issues puppetlabs-sqlserver 3.3.0 has been released What it is: sqlserver is a module that manages MS SQL Server 2012, 2014, 2016, 2017, 2019 and 2022 on Windows systems Where you can find it: - https://forge.puppet.com/modules/puppetlabs/sqlserver/readme - https://github.com/puppetlabs/puppetlabs-sqlserver/blob/main/CHANGELOG.md Key features/changes: Added - Support for SQL Server 2022 Feedback: - https://github.com/puppetlabs/puppetlabs-sqlserver/issues Slack Conversation

PDK 2.7 has been released The Puppet Development toolkit (PDK) provides integrated testing tools and a command line interface to help you develop, validate, and test modules Where you can find it: - https://www.puppet.com/downloads/puppet-development-kit - https://community.chocolatey.org/packages/pdk/2.7.0.0 - https://www.puppet.com/docs/pdk/2.x/pdk_upgrading.html - https://www.puppet.com/docs/pdk/2.x/release_notes_pdk.html Key features/changes: - Added

A RedHat 9 compatible package has been added.

A new Puppet validator for Bolt plans has been added by community member jay7x.

PDK Templates have been updated to 2.7.2.

Puppet 7.23 has been added to the packages.

Ruby 2.7.7 is now the default runtime used by packaged versions of PDK.

The minimum ruby requirement has been raised to 2.5.9./op

- Changed

PDK no longer ships with OSX 10.15 packages.

Legacy i18n support has been removed.

- Fixed

Selecting a Puppet Enterprise version with

PDK_PE_VERSION

will resolve the latest puppet gem relative to the PE release.

The vendored puppet-lint plugins have been updated to their latest compatible versions. This resolves an issue that top scope facts to be formatted incorrectly.

Deprecation warnings for

bundle show

will no longer be displayed when using the

release

command.

Feedback: - https://github.com/puppetlabs/pdk/issues - https://github.com/puppetlabs/pdk-templates/issues

@Robert FD the ticket has now moved to our public jira https://puppet.atlassian.net/browse/SERVER-3228 and I am unable to update it due to some transisition permissions issues but I did get the following response "The limit of 3 million codepoints is quite large and we find users who surpass that either have files that are unwieldy and should instead be integrated with a DB (eg hiera_vault), or are inserting large values that should instead be handled by a file resource. We recommend users do not surpass the limit instituted by SnakeYAML.. However, JRuby will support configuring SnakeYAML limits in 9.4. Because JRuby 9.4 implements Ruby 3.1 we will be shipping it in Puppet Platform 8/Puppet Server 8. If they backport the configuration to JRuby 9.3 then we will also take it up in Puppet Server 7. Configuring JRuby to adjust the SnakeYAML limit will be possible via JAVA_ARGS in the defaults file. Depending on user demand we may look into providing a way via Puppet Server's config to configure the limits once JRuby supports doing so, but that would be quite a ways out. "

Is it possible to add a compiler to a low latency site? Are there any recommendations on latency/jitter within PE infrastructure? A PE customer asks for such a setup.

This message was deleted.

How close should PE Primary Server and Agents be with release versioning. ? We run 2021.7.1 Primary what is the supported agent version? We were installing 2021.7.1 but would 2021.7.2 also be acceptable as it appears to be a part of the major release?

2021.7.2 on agent would work with 2021.7.1 on Primar/Master ? I guess that is my question

I tried to find 2021.7.2 agent release notes and cant find any..

It will be compatible

You can see components here https://www.puppet.com/docs/pe/2021.7/component_versions_in_recent_pe_releases.html

And information about server/client capability as well

ah cool

There are several changes you might have to do when switching between major puppet versions, but .z release usually going unnoticed

hmm ok gocha

So 2021.7.2 is still an LTS

Anything with a .z is part of the LTS train. The PE (Feature) train only has x.y.0.

Although, I guess 2021.7.0, which was the start of the LTS train only had a .0....