https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • s
    This message was deleted.
    🙌 1
    o
    b
    +2
    • 5
    • 12
  • b
    again, checkout the puppet-zabbix update, that does all this for you
  • s
    This message was deleted.
    this is fine fire 1
    s
    • 2
    • 2
  • o
    Yep, also noticed it 🙂 Looking forward to see package present on apt.puppet.com https://groups.google.com/g/puppet-users/c/C2zTWPU5tKA
  • s
    package for puppet-agent where available yesterday, today I see another directory for puppet7-release and the package is also in /.
  • s
    This message was deleted.
    j
    • 2
    • 3
  • s
    This message was deleted.
    j
    • 2
    • 1
  • n
    https://puppet.com/docs/puppet/7/server/subcommands.html#available-actions Assuming you’re on Puppet 6 or higher, you want 
    puppetserver ca revoke --certname <name>
    The 
    puppet ssl clean
    command is meant to be run on a Puppet agent to remove its own certificate, not to revoke a client certificate.
  • n
    https://puppet.com/docs/puppet/7/server/subcommands.html#available-actions Assuming you’re on Puppet 6 or higher, you want 
    puppetserver ca revoke --certname <name>
    If you just want to delete a client’s certificate from the CA, use 
    clean
    instead of 
    revoke
    . The 
    puppet ssl clean
    command is meant to be run on a Puppet agent to remove its own certificate, not to revoke a client certificate.
  • s
    This message was deleted.
    j
    n
    g
    • 4
    • 6
  • s
    This message was deleted.
    j
    r
    +2
    • 5
    • 20
  • s
    This message was deleted.
    b
    v
    n
    • 4
    • 24
  • v
  • v
  • v
    seems hardcoded
  • r
    class profile::la (optional[String] $FOO){ $bar = $profile::la::$FOO::bar}
  • n
    Yeah, 
    x86_64
    is hardcoded in the Cask formula, which is wrong now.
  • n
    Yeah, 
    x86_64
    is hardcoded in the Cask formula, which is wrong now.
  • v
  • v
  • s
    This message was deleted.
    h
    s
    • 3
    • 3
  • s
    This message was deleted.
    👍 1
    h
    y
    • 3
    • 8
  • k
    message has been deleted
  • k
    Hi , am getting this error while tying to fetch catalog from puppet master - Warning: Unable to fetch my node definition, but the agent run will continue: Warning: getaddrinfo: Name or service not known Info: Retrieving pluginfacts Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet//&lt;puppetserver&gt;/pluginfacts getaddrinfo: Name or service not known Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate': getaddrinfo: Name or service not known Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve file metadata for puppet///&lt;puppetserver&gt;/plugins getaddrinfo: Name or service not known Info: Loading facts Error: Could not retrieve catalog from remote server: getaddrinfo: Name or service not known Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: getaddrinfo: Name or service not known
  • k
    Can any one suggest a solution ?
  • b
    sounds like your DNS is broken?
  • k
    should i edit resolv.conf file?
  • b
    do you have a working resolver in that file? can you resolve other domain names? is your puppet agent trying to reach 
    puppet
    and not a proper fqdn? was it working before?
  • k
    recently the servers were migrated to a pvt cloud
  • k
    i am getting correct ip with nslookup
1...118119120...428Latest