are there any plans to have RHEL 9 agent support on ppc64le (POWER) architectures?

This message was deleted.

This message was deleted.

Use the concat module to merge multiple sources into one file.

no. it will trigger that refreshonly

Couple

puppet.conf

questions: 1. Are the

[master]

and

[server]

sections synonymous? I just discovered that mine have

[master]

sections, but the documentation calls it

[server]

, but mine still work. I’m wondering when it just breaks. I don’t recall getting deprecation notices on this. 2. If there are duplicate sections with different parameters in them, will they get merged? I’ve discovered some concat::fragment overlap in my company’s management of this file and plan to switch to using inifile, but I want to understand how to organize my repair plan.

This message was deleted.

they are probably aliases for now

is there an rss feed for puppet product announcements or is google groups the primary place to watch?

I use https://puppet.com/blog/rss.xml, but it's not very active

mail lists are used for updates

This message was deleted.

Hello all. Trying to figure this one out. I know it's possible, but can't figure out how to do it. In hiera I have something like:

topics:
  topic1:
    modules:
      - module1
      - module2
      - module3
  topic2:

in the puppet profile, I am looping through topics:

topics = lookup('topics')
$topics.each |$topic, $values| {

and then passing values to a file resource using an epp template. In the template I am doing:

<% if 'modules' in $values { -%>
foo.modules:<% $values.get('modules').then |$module| { -%> 
  <% $module.each |$mod| { %>
  - module: <%= $mod -%>

This lists each module like so:

foo.modules:
- module: module1
- module: module2
- module: module3

Everything works fine. I am wanting to now do something like this in hiera:

topics:
  topic1:
    modules:
      module1:
        foo.enabled: true
        bar.enabled: false
      module2:
      module3:
  topic2:
   modules:
     - module1
     - module2
     - module3

Notice there are still arrays for modules, but some have.. sub keys. I want to loop through the modules such that, if there are sub keys, they will be added via the epp.

- module: module1
  foo.enabled: true
  bar.enabled: false
- module: module2
- module: module3

Is this possible?

Hello all. Trying to figure this one out. I know it's possible, but can't figure out how to do it. In hiera I have something like:

topics:
  topic1:
    modules:
      - module1
      - module2
      - module3
  topic2:

in the puppet profile, I am looping through topics:

topics = lookup('topics')
$topics.each |$topic, $values| {

and then passing values to a file resource using an epp template. In the template I am doing:

<% if 'modules' in $values { -%>
foo.modules:<% $values.get('modules').then |$module| { -%> 
  <% $module.each |$mod| { %>
  - module: <%= $mod -%>

This lists each module like so:

foo.modules:
- module: module1
- module: module2
- module: module3

Everything works fine. I am wanting to now do something like this in hiera:

topics:
  topic1:
    modules:
      module1:
        foo.enabled: true
        bar.enabled: false
      module2:
      module3:
  topic2:
   modules:
     - module1
     - module2
     - module3

Notice there are still arrays for modules, but some have.. sub keys. I want to loop through the modules such that, if there are sub keys, they will be added via the epp.

foo.modules:
- module: module1
  foo.enabled: true
  bar.enabled: false
- module: module2
- module: module3

Is this possible?

This message was deleted.

This message was deleted.

The Puppet 6 docs referred to it as

[server]

, too

The Puppet 6 docs referred to it as

[server]

, too

This message was deleted.

trying to sort out how to make the transition from

puppet cert sign ${client_certname}

on my pm5 puppetserver. Even after resetting the ca_port to 8140 and restarting the puppetserver, it still seeks to connect on my ${masterport}, 8240. Details:

# puppetserver ca sign --certname efc9c26-01275.dev.${project_code}.${client_domain}.org 
Fatal error when running action 'sign'
  Error: Failed connecting to <https://pm5>.${my_domain}.com:8240/puppet-ca/v1/certificate_status/
  Root cause: Failed to open TCP connection to pm5.${my_domain}.com:8240 (Connection refused - connect(2) for "pm5.${my_domain}.com" port 8240)

Any thoughts on what is required to resolve this would be much appreciated. Thank you for your time.

Look at

/etc/puppetlabs/puppet/puppet.conf

on that machine. Are you sure the CA port is fixed?

also, make sure you're running that command as root.

@natemccurdy thanks for the input! Sorry I missed it yesterday. That file indicates that server.ca_port = 8140. also, yes to running as root, and this:

# puppet config --section server print | grep ca_port 
ca_port = 8140

Are there other

ca_port

settings in other sections? Like [main]?

This message was deleted.

I have the following on file

/etc/systemd/system/puppet.service.d/wants.conf

on my puppet server:

[Unit]
Wants=basic.target puppetserver.service
After=basic.target network.target puppetserver.service

Perhaps that will solve your issue.

I have the following file

/etc/systemd/system/puppet.service.d/wants.conf

on my puppet server:

[Unit]
Wants=basic.target puppetserver.service
After=basic.target network.target puppetserver.service

Perhaps that will solve your issue.

This message was deleted.

I would consider designing roles in a way that each node has only one role.

honestly not sure If I did right or not but I created a profile for main project and included main project module there, then created a second profile called docker and added docker component module with some modifications like version and so. On role seperately added project profile and docker profile.