https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • c
    Yes thank you. Was just not aware that the default value ist just applied when the parameter is not definded at all. Puppet handle that in an other way than ruby 🤷
  • b
    @whatsaranjit can you maybe take a look at https://github.com/WhatsARanjit/puppet-node_manager/pull/70 and also do a 1.0.0 release?
  • b
    @whatsaranjit can you maybe take a look at https://github.com/WhatsARanjit/puppet-node_manager/pull/70 and also do a 1.0.0 release?
  • v
    there bunch of PRs waiting there if I recall, I think Ranjit lost interest 😞
    sadpanda 1
  • j
    Be nice if we could get some movement on https://github.com/puppetlabs/puppetlabs-apt/pull/1073
  • j
    Be nice if we could get some movement on https://github.com/puppetlabs/puppetlabs-apt/pull/1073
  • o
    tryhing to move to puppet 7 and updating my modules however I get warnings like: Info: Using environment 'test' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Warning: The current total number of facts: 4113 exceeds the number of facts limit: 2048 any advices to go about this ?
  • s
    This message was deleted.
    o
    • 2
    • 1
  • v
    alternatively, block some facts you don't care about
  • c
    that is a metric crap-ton of facts. I’ve never had the occasion to either have or encounter such a large number of facts
  • v
    I agree, we have maybe 200 or so
  • y
  • y
    Btw.. is there any metric exposed on facts amount (in items and/or in bytes) per node?
  • y
    I believe it’s possible to grab the numbers from the PuppetDB though..
  • v
    yeah, but that bug actually says, it's a bigger value 🙂
    😞 1
  • v
    so when it gets fixed there will be more 🙂
  • v
    The good news it's a soft limit, it's just a proactive warning on Puppet part to pay attention to excessive data
  • s
    This message was deleted.
    j
    • 2
    • 1
  • y
    AWS instance? I ran into that in AWS with instances launched with a base64-encoded cloud-init script.
    💯 1
  • y
    AWS instance? I ran into that in AWS with instances launched with a base64-encoded cloud-init script.
  • o
    no just some CentOS vm that previously ran puppet 5, i moved to puppet 7 and updated my modules, which compiles and runs just warns about the many facts. if i exclude the facts as described in the facter.conf snippet i get that error
  • o
    running facter directly gives an answer: [root@vwd-vh01-stage ~]# facter -p [2023-02-27 175153.532228 ] ERROR Facter - Error while resolving custom fact fact='network_primary_interface', resolution='<anonymous>': undefined method `[]' for nil:NilClass [2023-02-27 175153.643921 ] ERROR Facter - Error while resolving custom fact fact='network_primary_ip', resolution='<anonymous>': undefined method `[]' for nil:NilClass aio_agent_version => 7.23.0
  • v
    blocking networking is probably overkill?
  • v
    most of required facts are there
  • o
    myeah, and memory too, but that was a typo
  • o
    i don't really need all facts off all my container and mountpoints and container networking facts
  • o
    kept it on blocking filesystem and docker
  • m
    message has been deleted
  • k
    Can someone please point me in the right direction trying to create DNS-alt-names for puppet server? I'm following the latest guide - https://www.puppet.com/docs/puppet/7/ssl_regenerate_certificates.html#regenerate_agent_certs_and_add_dns_alt_names
  • k
    Fresh install, latest version of puppet, it's up and running, listening on 8140, etc. Everythings hunky dory. Then I'm just following the directions above - root@puppet:~ # puppetserver ca clean --certname puppet.lan Certificate for puppet.lan has been revoked Cleaned files related to puppet.lan root@puppet:~ # puppet ssl clean Notice: Removed private key /var/puppet/ssl/private_keys/puppet.lan.pem Notice: Removed public key /var/puppet/ssl/public_keys/puppet.lan.pem Notice: Removed certificate /var/puppet/ssl/certs/puppet.lan.pem root@puppet:~ # puppet resource service puppetserver ensure=stopped Notice: /Service[puppetserver]/ensure: ensure changed 'running' to 'stopped' service { 'puppetserver': ensure => 'stopped', provider => 'freebsd', } root@puppet:~ # puppetserver ca generate --certname puppet --subject-alt-names 'puppet,puppet.lan,puppet1,puppet1.lan' --ca-client /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/local_certificate_authority.rb158in `sign_authorized_cert': undefined method `subject' for nil:NilClass (NoMethodError) from /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/action/generate.rb191in `block in generate_authorized_certs' from /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/action/generate.rb180in `map' from /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/action/generate.rb180in `generate_authorized_certs' from /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/action/generate.rb161in `run' from /usr/local/lib/ruby/gems/3.0/gems/puppetserver-ca-2.3.6/lib/puppetserver/ca/cli.rb💯in `run' from /usr/local/share/puppetserver/cli/apps/ca5in `<main>'
1...313314315...428Latest