I guess it’s more like

classes:
  puppet::params:
    version: 6

Thank you! The proper hiera syntax is:

mysql::server::override_options:

mysqld:

pid-file: "/var/lib/mysql/%{::fqdn}.pid"

Thank you! The proper hiera syntax is:

mysql::server::override_options:

mysqld:

pid-file: "/var/lib/mysql/%{::fqdn}.pid"

Thank you! The proper hiera syntax is:

mysql::server::override_options:

mysqld:

pid-file: "/var/lib/mysql/%{::fqdn}.pid"

FYI: I have to do this because the puppet-mysql module doesn't quite support MariaDB Enterprise because /var/run/mariadb directory is neither created by the mariadb RPM nor the puppet-mysql module.

Thank you! The proper hiera syntax is:

mysql::server::override_options:

mysqld:

pid-file: "/var/lib/mysql/%{::fqdn}.pid"

FYI: I have to do this because the puppet-mysql module doesn't quite support MariaDB Enterprise because /var/run/mariadb directory (the default that puppet-mysql configures) is neither created by the mariadb RPM nor the puppet-mysql module.

Hi Puppeteers, When I run puppet agent on a windows server with puppet version 7.10. I get error facts.yaml as legacyFacter:utilparser:YamlParser facts: invalid byte sequence in UTF-8

Looks like puppet complier is not able to read whole windows services. Also I see csr_attribute file is not getting created

Error: Factor: Failed to handle facts file.yaml as legacyFactor:utilParser:YamlParser facts: invalid byte sequence in UTF-8

I’m seeking help . Can anyone pls help me

Hi @krishna kant mishra I believe this is related to https://tickets.puppetlabs.com/browse/FACT-1902 , is this after you have added your own custom / external fact ? @csharpsteen maybe able to advise on this as well I think he's familiar with this error

Yes

We have this issue on couple of servers

Yup. String values returned as facts have to be in UTF-8 encoding and cannot include

\0

, the null byte.

Hello. Are there any plans to release a Debian package of puppet agent 6 for arm64? Little bit annoying being unable to use puppet on arm-based machines

I see arm64, armel, and armhf in the repo

apt.puppetlabs.com?

Aye. https://apt.puppetlabs.com/dists/bullseye/puppet6/index.html

There are packages of puppetserver, but not the agent, see http://apt.puppetlabs.com/pool/bullseye/puppet6/p/puppet-agent/index.html

huh ... Packages indicates it is just the -release .deb, not the agent

It's available for Ubuntu 20.04, but not 22.04 and none for Debian.

It is in the jessie (wow, that's old) pool ... ¯\_(ツ)_/¯ May want to stick around for an "official" answer rather than a 2nd set of eyes looking at the apt site.

It is in the jessie (wow, that's old) and buster pools ... ¯\_(ツ)_/¯ May want to stick around for an "official" answer rather than a 2nd set of eyes looking at the apt site.

It is in the jessie (wow, that's old) pool ... ¯\_(ツ)_/¯ May want to stick around for an "official" answer rather than a 2nd set of eyes looking at the apt site.

It is in the jessie (wow, that's old) pool ... ¯\_(ツ)_/¯ May want to stick around for an "official" answer rather than a 2nd set of eyes looking at the apt site.

Brace yourselves... https://github.com/reidmv/puppet-module-puppet_certificate/pull/11

I thought I would repost this at a later time. Looking at existing mysql installations with the changes in

puppetlabs-mysql

.

See the

puppetlabs-mysql

module at https://forge.puppet.com/puppetlabs/mysql?src=slack&channel=puppet

This message was deleted.

I'm looking for advice on how to handle Red Hat subscription-manager management. I'm using waveclaw-puppet but every time it runs I get a notification:

Notice: /Stage[main]/Subscription_manager::Config/Rhsm_register[<http://subscription.rhn.redhat.com|subscription.rhn.redhat.com>]/ensure: created (corrective)

The other problem that I have is that I'm unsure how to enforce that the subscription-manager module runs before everything because yum/dnf and everything relying on rpm-based packages relies on the system being subscribed properly to Red Hat (or in my case an internal RH Satellite server). I'm using Terraform to create the virtual machines on both VMWare and Oracle cloud. I have cloud-init at my disposal on Oracle cloud but not in the VMware environment. Terraform clones a gold image that I have that is not registered to my satellite server because if it were registered, the cloning of that gold image would cause subscription manager issues on the newly-provisioned server. I'm open for suggestions. I can deal with the Notice: happening as it's more annoying than anything else but I've not been successful in guaranteeing that the subscription manager module runs before everything else.

The fact, rhsm_ca_name is returing an empty string (or undef) which causes this part of the code to keep re-registering. I haven't figured out why rhsm_ca_name fact is empty but I'm sure it has something to do with none of the files in the ruby code being found.