I thought PE would use bolt to login to the node, then the nodes puppet agent to to apply the lookup

I thought PE would use bolt to login to the node, then the nodes puppet agent to to apply the lookup Essentially the same thing that happens when i run the bolt executable from my laptop against a target (where the lookup does work)

Can I iterate types?

This message was deleted.

That should work for any resource type I'd think, but I'm not sure .

indeed 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T

I’m try add mount point path outside puppet directories in puppet server , I configure fileserver.conf but show this error “Not autorízed to call find on /file_metadata/ permissions are right, any idea ?

This message was deleted.

hello folks. is the Dockerfile for the puppet-agent image available somewhere? the linked repo on the hub there doesn't seem to have it...

hello folks. is the Dockerfile for the puppet-agent image available somewhere? the linked repo on the hub there doesn't seem to have it...

there are no officially supported docker images anymore

gotcha. ok, thanks

This message was deleted.

Hi Add the new names ot the main section of the puppet.conf on the client

[main]
...
dns_alt_names = puppet, <http://test.xyz.com|test.xyz.com>, <http://test.abc.com|test.abc.com>

then

rm -rf /etc/puppetlabs/puppet/ssl/

then

puppetserver ca clean --certname <http://test.xyz.com|test.xyz.com>

then run on the client to force creating a new SSL

puppet agent -t

Hi Add the new names to the main section of the puppet.conf on the client

[main]
...
dns_alt_names = puppet, <http://test.xyz.com|test.xyz.com>, <http://test.abc.com|test.abc.com>

then

rm -rf /etc/puppetlabs/puppet/ssl/

then

puppetserver ca clean --certname <http://test.xyz.com|test.xyz.com>

then run on the client to force creating a new SSL

puppet agent -t

you are right, I thought mybe there is a way to learn something new... so Ill do it here: https://www.puppet.com/docs/puppet/7/ssl_regenerate_certificates.html Thanks a lot @ssaini

This message was deleted.

Hi, is there a way to look up another hosts IP address and give it to a resource? this block loops around a list of compiler names, but I am not sure how to get the IP and pass to ipaddresses (without having to define anywhere)

$compilers.each |$compiler| {
    haproxy::balancermember { $compiler:
      listening_service      => 'puppet',
      server_names           => $compiler,
      ipaddresses            => [getIP],
      ports                  => '8140',
      options =>             'check',
    }
  }

message has been deleted

Oh, woops, sorry, I link I sent was to the entire page. It should've been to this specific section: https://www.puppet.com/docs/puppet/7/ssl_regenerate_certificates.html#regenerate_agent_certs_and_add_dns_alt_names

This message was deleted.

message has been deleted

This message was deleted.

See the

puppet-puppetserver

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

Here's what I did in a similar situation in my hiera file:

# override yum repo mariadb version

mariadb::repo::repo_version: '10.5.18-13'  # The - here doesn't match yum versionlock.  That's OK!

mariadb::server::manage_repo: false   # We'll manage our own MariaDB Enterprise repos. (below)

Also, you have to ensure that the mariadb enterprise repositories are defined in /etc/yum.repos.d:

yum::managed_repos:

- "mariadb-es-main"

- "mariadb-maxscale"

- "mariadb-tools"

- "mariadb-enterprise-tools"

In addition, I had to versionlock the MariadDB RPM so that yum wouldn't try to upgrade it:

yum::versionlock:

'MariaDB-server':

ensure: present

version: '10.5.18_13'

release: "1.el%{::os.release.major}"

epoch: 0

arch: "%{::os.architecture}"

Here's what I did in a similar situation in my hiera file:

# override yum repo mariadb version

mariadb::repo::repo_version: '10.5.18-13'  # The - here doesn't match yum versionlock.  That's OK!

mariadb::server::manage_repo: false   # We'll manage our own MariaDB Enterprise repos. (below)

Also, you have to ensure that the mariadb enterprise repositories are defined in /etc/yum.repos.d:

yum::managed_repos:

- "mariadb-es-main"

- "mariadb-maxscale"

- "mariadb-tools"

- "mariadb-enterprise-tools"

In addition, I had to versionlock the MariadDB RPM so that yum wouldn't try to upgrade it:

yum::versionlock:

'MariaDB-server':

ensure: present

version: '10.5.18_13'

release: "1.el%{::os.release.major}"

epoch: 0

arch: "%{::os.architecture}"

yum::repos:

"mariadb-es-main":

descr: "MariaDB Enterprise Server"

baseurl: "<https://dlm.mariadb.com/repo/your_mariadb_id_here/mariadb-enterprise-server/%{lookup('mariadb::repo::repo_version')}/rpm/rhel/%{::os.release.major}/%{::architecture}>"

enabled: true

gpgcheck: true

gpgkey: "<https://supplychain.mariadb.com/MariaDB-Enterprise-GPG-KEY>"

module_hotfixes: true

target: "/etc/yum.repos.d/mariadb.repo"

"mariadb-maxscale":

descr: "MariaDB MaxScale"

baseurl: "<https://dlm.mariadb.com/repo/your_mariadb_id_here/maxscale/latest/yum/rhel/%{::os.release.major}/%{::architecture}>"

enabled: true

gpgcheck: true

gpgkey: "<https://supplychain.mariadb.com/MariaDB-MaxScale-GPG-KEY>"

target: "/etc/yum.repos.d/mariadb.repo"

"mariadb-tools":

descr: "MariaDB Tools"

baseurl: "<https://downloads.mariadb.com/Tools/rhel/%{::os.release.major}/%{::architecture}>"

enabled: true

gpgcheck: true

gpgkey: "<https://supplychain.mariadb.com/MariaDB-Enterprise-GPG-KEY>"

target: "/etc/yum.repos.d/mariadb.repo"

"mariadb-enterprise-tools":

descr: "MariaDB Enterprise Tools"

baseurl: "<https://dlm.mariadb.com/repo/your_mariadb_id_here/enterprise-tools/latest/rpm/rhel/%{::os.release.major}/%{::architecture}>"

enabled: true

gpgcheck: true

gpgkey: "<https://supplychain.mariadb.com/MariaDB-Enterprise-GPG-KEY>"

module_hotfixes: true

target: "/etc/yum.repos.d/mariadb.repo"

This message was deleted.

note that these docker images aren't maintained anymore. https://github.com/puppetlabs-toy-chest/puppetserver-docker

Anyone else have trouble with agents failing to check-in after resuming from suspend?

Mar 02 08:00:03 laptop01 puppet-agent[57764]: Connection to <https://puppet.example.com:8140/puppet/v3> failed, trying next route: Request to <https://puppet.example.com:8140/puppet/v3> failed after 0.038 seconds: Failed to open TCP connection to <http://puppet.example.com:8140|puppet.example.com:8140> (getaddrinfo: Temporary failure in name resolution)
Mar 02 08:00:03 laptop01 puppet-agent[57764]: Wrapped exception:
Mar 02 08:00:03 laptop01 puppet-agent[57764]: Failed to open TCP connection to <http://puppet.example.com:8140|puppet.example.com:8140> (getaddrinfo: Temporary failure in name resolution)
Mar 02 08:00:03 laptop01 puppet-agent[57764]: No more routes to fileserver

The agent tries to contact the puppet server before it has properly woken up, so network and name resolution aren't working. I've seen this reddit post with the same issue, but no definitive answer: https://www.reddit.com/r/Puppet/comments/7um9tb/getaddrinfo_temporary_failure_in_name_resolution/

it looks like your dns configuration/network is slower than the puppet agent