Maybe it is reading a different hiera.yaml? Or in a different environment, Check the paths.

and adding --compile on the CLI is also helpful. especially in this case, where you use topscope variables in hiera.yaml

Or, there is a difference in the set of facts.

ty both! I already tried

--compile

and lookup command is not an issue it is able to find and process the hiera entry, lookup function is simply skipping the

Hierarchy entry

it only picks up the name, but doesn't process the paths, and skips to next

Hierarchy entry

😞

ok I've found what it is... hopefully this will help someone if anyone runs into similar issue... I'm performing these tests on my lab environment, using VScode with SSH directly to my code path... so all new files in that hiararchy entry path ended up 0700 root:root 😞 puppet lookup command -> ran with sudo, puppet run runs as pe-puppet user so it needs access 😞 Thank you all for your input (and I hope this will help next silly person that tests things the way I do 😢 )

ok I've found what it is... hopefully this will help someone if anyone runs into similar issue... I'm performing these tests on my lab environment, using VScode with SSH directly to my code path... so all new files in that hiararchy entry path ended up 0700 root:root 😞 puppet lookup command -> ran with sudo, puppet run runs as pe-puppet user so it needs access 😞 Thank you all for your input (and I hope this will help next silly person that tests things the way I do 😢 )

Good news! Turns out I'm dumb and didn't realize that the

.puppet-lint.rc

file actually WAS working. There were just some new checks that weren't documented on the puppet-lint website included in the PDK for parameter documentation and I thought they were supposed to be turned off by the

--no-documentation-check

setting, but it turns out, I was wrong. I found the relevant checks via

pdk bundle exec puppet-lint --help

and then turned them off and it worked as expected. Thanks to everyone for your ideas and support.

Day 8 posted: https://github.com/puppetlabs/community/discussions/28#discussioncomment-4344810 This was a fun one!

This message was deleted.

You could also generate the array and reverse it

the reason is: https://github.com/puppetlabs/community/discussions/28

Is there a way to set DNS_ALT_NAMES or change the CN for the puppetdb cert (via the deb install method) like how the puppetdb docker image allow you to?

This message was deleted.

Been dealing with an issue on Solaris with insync() in

lib/puppet/provider/package/pkg.rb

, specifically in a global zone with a lot of non-global zones (one of mine has 75 of them), an

pkg update -n

to verify the correct version of a package is both enormously expensive, and, if we are running puppet in the zones, doomed to fail. It seems to me that the information we want already exists in the output of the

pkg(:list, '-Hvfa', "#{name}@#{should}")

, in that if the final column has an “i” in it, then that states that tis is the version that is currently installed.

This message was deleted.

This message was deleted.

Hello everybody, not sure this is a correct place. I think to have found a bug in facter affecting the diskless node configured to run "puppet apply": puppetserver version: 7.9.2 puppet agent version: 7.20.0 facter version: 4.2.13

[root@sbc]# facter partitions
[2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass

Likely the issue does not prevent the correct configuration of the nodes, but it produce an error: Error: Facter: undefined method `[]' for nil:NilClass

Hello everybody, not sure this is a correct place. I think to have found a bug in facter affecting the diskless node configured to run "puppet apply": puppetserver version: 7.9.2 puppet agent version: 7.20.0 facter version: 4.2.13

[root@sbc]# facter partitions
[2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass

Likely the issue does not prevent the correct configuration of the nodes, but it produce an error: Error: Facter: undefined method `[]' for nil:NilClass

Please do file a FACT ticket

Hi @josh! How one can register in the Puppet Jira these days? Ppl are asking about this frequently..

This message was deleted.

message has been deleted

This message was deleted.

Hi, Question about hash 'addition' in puppet DSL. I currently on (PE) puppet 6 and will be going to 7 sometime next year. I really like the new way to deal with hashes. So

newhash = hash1 + hash2

Works well for me, entries with common keys from hash2 override and replace those in hash1 Can I do something like:

newhash = (hash1 + hash2) + hash3

Seems like you should. Thanks

Maybe but I can't learn the hard lessons on my own if I use Puppet Lab's modules (and, iirc, this one is kinda terrible).

Hello everybody, not sure this is a correct place. I think to have found a bug in facter affecting the diskless node configured to run "puppet apply": puppetserver version: 7.9.2 puppet agent version: 7.20.0 facter version: 4.2.13

[root@sbc]# facter partitions
[2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass

Likely the issue does not prevent the correct configuration of the nodes, but it produce an error: Error: Facter: undefined method `[]' for nil:NilClass.

Hello everybody, not sure this is a correct place. I think to have found a bug in facter affecting the diskless node configured to run "puppet apply": puppetserver version: 7.9.2 puppet agent version: 7.20.0 facter version: 4.2.13

[root@sbc]# facter partitions
[2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass

Likely the issue does not prevent the correct configuration of the nodes, but it produce an error: Error: Facter: undefined method `[]' for nil:NilClass. Added: I believe that the bug is in "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/facts/linux/partitions.rb" line 9: the possibility of not having a disk and therefore a partitions is not accounted for.

I'm troubleshooting an issue with UFW on my Ubuntu 20.04 puppetserver, after about 24 hours or so it'll start blocking Puppet traffic for some reason, leaving trails like this even though port 8140 is explicitly allowed.

Dec  8 14:47:19 vmpuppetmaster01 kernel: [ 1521.332427] [UFW BLOCK] IN=ens160 OUT= MAC=00:50:56:95:ad:31:74:ac:b9:3a:65:1b:08:00 SRC=192.168.60.10 DST=192.168.4.62 LEN=52 TOS=0x00 PREC=0x00 TTL=63 ID=23093 DF PROTO=TCP SPT=59528 DPT=8140 WINDOW=64240 RES=0x00 SYN URGP=0

Reloading UFW will temporarily resolve it, but I'm currently scratching my head.

It does the same with CheckMK (6556) as well