https://www.puppet.com/community logo
Join Slack
Powered by
# puppet-enterprise
  • g
    From a support perspective we recommend that the agent version is in line with the Primary version and not ahead as there can be subtleties in agents version that require the primary to be the same. Having the agent on a lower version would also be supported but ideally with respect to upgrading to align in due course.
  • c
    Ideally, agents should be at the same version as the Primary and other infrastructure. They can trail behind and there is testing to ensure compatibility up to one major version back. There is no testing checking for forward compatibility. Most of the time you'll get lucky, especially with .z releases within th the same series. But. I want to be very clear: there is no testing and no guarantees around forward compatibility outside of specific scenarios that have been manually spot checked.
    👍 1
  • s
    This message was deleted.
    b
    s
    z
    • 4
    • 8
  • z
    Does anyone know if it's possible to limit the number of API calls by a specific RBAC user to the main Puppet server?
  • s
    This message was deleted.
    t
    r
    +2
    • 5
    • 12
  • s
    This message was deleted.
    b
    t
    +3
    • 6
    • 7
  • d
    Puppet Integration Releases ServiceNow Service Graph Connector for Puppet 1.2.0 The Service Graph Connector for Puppet ingests data from multiple Puppet Enterprises directly into ServiceNow’s CMDB to give you and your team rich, relevant data to make informed decisions across your on-prem and cloud infrastructure. Increase the data share frequency and wealth of information on each resource in the form of Facts, collected by the Puppet Agent and shared directly into the ServiceNow CMDB for real-time data advantage. Key features/changes: • Users are able to import data to ServiceNow from Multiple Puppet Enterprises using this version. • Added new relationships for multiple network interfaces CMDB • Certified to ServiceNow Tokyo Support Contact Puppet Integrations Engineering team-pie@puppet.com Find out more https://www.puppet.com/integrations/servicenow
    yay 2
  • d
    Also check out https://github.com/puppetlabs/puppetlabs-pecdm and https://forge.puppet.com/modules/puppetlabs/peadm Which help automate deployment of PE standard architectures
  • d
    Puppet Integration Releases ServiceNow Service Graph Connector for Puppet 1.2.0 The Service Graph Connector for Puppet ingests data from multiple Puppet Enterprises directly into ServiceNow’s CMDB to give you and your team rich, relevant data to make informed decisions across your on-prem and cloud infrastructure. Increase the data share frequency and wealth of information on each resource in the form of Facts, collected by the Puppet Agent and shared directly into the ServiceNow CMDB for real-time data advantage. Key features/changes: • Users are able to import data to ServiceNow from Multiple Puppet Enterprises using this version. • Added new relationships for multiple network interfaces CMDB • Certified to ServiceNow Tokyo Support Contact Puppet Integrations Engineering team-pie@puppet.com Find out more https://www.puppet.com/integrations/servicenow
  • s
    This message was deleted.
    d
    b
    • 3
    • 8
  • d
  • d
    if there is a csr signing file /etc/puppetlabs/puppet/csr_attributes.yaml on any of the infra nodes it will merge it with the peadm specfic csr attributes https://github.com/puppetlabs/puppetlabs-peadm/blob/501aa363c5bd60f94e5931cead6cdfe2349b6856/plans/util/insert_csr_extension_requests.pp#L2
  • s
    This message was deleted.
    b
    i
    • 3
    • 30
  • i
    Hello, we are running puppet in enforce using the cron once in 24Hrs. We’re seeing some weird issue. For some reason, one of the fact which was there all this time is no more displaying on the puppet console. However, it exists on the server. And, once we run the puppet manually(exactly same command which is configured in the cron) the fact is being displayed in the console. I would like to understand why the fact is missing initially and why I’ve to run puppet manually to display the fact on the puppet console? I’m not seeing any issues on the server.
  • b
    a common issue is that some environment variables are missing when stuff is executed via cron
  • i
    Here is the fact code: Facter.add(“pbversion”) do confine :kernel => :linux setcode do if File.exist? ‘/etc/pb.cfg’ Facter:Util:Resolution.exec(‘pbrun -v 2>&1 | grep -o \’Version [0-9.-]*\’ | awk \’{print $2}\’’) else %x{echo absent}.chomp end end end
  • i
    One thing we changed in the fact code is the way we’re getting the version. Previously, we were using the below instead of Facter::Util. %x{grep inst_manifest_version /etc/pb.cfg | awk -F ‘=‘ ‘{print $2}’ | tr -d “‘“}.chomp
  • s
    This message was deleted.
    m
    • 2
    • 1
  • k
    I am still not grasping something with how pathing works when trying to copy a file using the file function. I have a base.pp profile located here:
    Copy code
    dmin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux# ls -al
total 20
drwxr-x--- 4 pe-puppet pe-puppet 4096 Apr  3 19:40 .
drwxr-x--- 3 pe-puppet pe-puppet 4096 Apr  3 16:20 ..
-rw-r----- 1 pe-puppet pe-puppet 1802 Apr  3 19:40 base.pp
drwxr-x--- 2 pe-puppet pe-puppet 4096 Apr  3 19:18 files
drwxr-x--- 2 pe-puppet pe-puppet 4096 Apr  3 16:20 manifests
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux#
    Which has:
    Copy code
    file { '/etc/snmp/snmpd.conf':
        ensure  => file,
        content => file("${module_name}/manifests/linux/files/conf.snmpd.debian.${facts['company_node_identification']['datacenter']}"),
    When I run it on my test agent I get:
    Copy code
    puppet agent -t
Info: Using environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, 
Evaluation Error: Error while evaluating a Function Call, Could not find any files from profile/manifests/linux/files/conf.snmpd.debian.ash 
(file: /etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux/base.pp, line: 28, column: 20) on node ash-test-99
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
    And I am 100% sure this file exists:
    Copy code
    admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules# ls -al
total 28
drwxr-x--- 7 pe-puppet pe-puppet 4096 Feb 24 16:22 .
drwxr-x--- 8 pe-puppet pe-puppet 4096 Apr  3 19:40 ..
drwxr-x--- 4 pe-puppet pe-puppet 4096 Jan 26 21:50 adhoc
drwxr-x--- 3 pe-puppet pe-puppet 4096 Feb  8 18:09 custom_facts
drwxr-x--- 3 pe-puppet pe-puppet 4096 Feb 24 16:22 firewall
drwxr-x--- 3 pe-puppet pe-puppet 4096 Apr  3 16:16 profile
drwxr-x--- 3 pe-puppet pe-puppet 4096 Feb 10 16:44 role
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules# cd profile/
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile# cd manifests/
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests# ls
example.pp  linux 
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests# cd linux/
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux# ls -al
total 20
drwxr-x--- 4 pe-puppet pe-puppet 4096 Apr  3 19:40 .
drwxr-x--- 3 pe-puppet pe-puppet 4096 Apr  3 16:20 ..
-rw-r----- 1 pe-puppet pe-puppet 1802 Apr  3 19:40 base.pp
drwxr-x--- 2 pe-puppet pe-puppet 4096 Apr  3 19:18 files
drwxr-x--- 2 pe-puppet pe-puppet 4096 Apr  3 16:20 manifests
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux# cd files/
admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux/files# ls -al
total 28
drwxr-x--- 2 pe-puppet pe-puppet 4096 Apr  3 19:18 .
drwxr-x--- 4 pe-puppet pe-puppet 4096 Apr  3 19:40 ..
-rw-r----- 1 pe-puppet pe-puppet  363 Apr  3 16:16 conf.snmpd.debian.ash

admin@pe-master:/etc/puppetlabs/code/environments/production/site-modules/profile/manifests/linux/files#
  • d
    drwxr-x- took a hit! Ouch. (Karma: -4)
  • k
    I have tried to move that file around to many different spots...in the directory tree...
  • v
    There is an article with layout of a module in documentation. your structure is wrong
  • v
    you should have in your module (I assume called profile) the following directories
    Copy code
    manifests/
files/
templates/
    and so on
  • v
    you should have in your module (I assume called profile) the following directories
    Copy code
    manifests/
files/
templates/
    and so on
  • v
    so, lets start from a class
  • v
    profile::linux
    class should be in 
    ${env}/site-modules/profile/manifests/linux.pp
  • v
    then this file 
    file("${module_name}/manifests/linux/files/conf.snmpd.debian.${facts['company_node_identification']['datacenter']}"),
    should really be a template, most likely
  • v
    but lets assume it's a file
  • v
    you probably want
    Copy code
    file("${module_name}/linux/conf.snmpd.debian.${facts['company_node_identification']['datacenter']}"),
    instead
  • v
    and this should be located in
    Copy code
    ${env}/site-modules/profile/files/linux/conf.snmpd.debian.corp.dc1
1...424344...73Latest