Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11755 each/map/filter functions are slow/buggy on jruby Change By: Josh Cooper Epic Link: PUP-11658 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481178.167581186.10434.1676447940022%40Atlassian.JIRA.
Jira (PUP-11726) Allow Puppet function calls from hiera data
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11726
Allow Puppet function calls from hiera data
Change By:
Josh Cooper
In combination with stdlib::manage I want to be able to use Puppet functions from hiera data. e.g. {code:java} stlib stdlib ::manage:: create_reosurces create_resources : file: '/etc/motd': ensure: file content: %{epp('profile/motd.epp')}{code} Actual result:{noformat}Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Unable to parse (/etc/puppetlabs/code/environments/production/data/common.yaml): found character '%' that cannot start any token. (Do not use % for indentation) while scanning for the next token at line 72 column 16{noformat}Desired result: The content is rendered from the template.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails
Jira (FACT-3185) facter os.windows.product_name incorrect value for Windows 11
Title: Message Title
Josh Cooper commented on FACT-3185
Re: facter os.windows.product_name incorrect value for Windows 11
Facter 4's current behavior for Windows 10 is:
"os": {
"architecture": "x64",
"family": "windows",
"hardware": "x86_64",
"name": "windows",
"release": {
"full": "10",
"major": "10"
},
"windows": {
"edition_id": "Enterprise",
"installation_type": "Client",
"product_name": "Windows 10 Enterprise",
"release_id": "2004",
Jira (FACT-3183) add djberg96/sys-proctable to gemset
Title: Message Title Josh Cooper commented on FACT-3183 Re: add djberg96/sys-proctable to gemset Hi Robert Waffen facter has a hard dependency on sys-filesystem because it allows us to generate core facts without reinventing the wheel. But I don't think any core facts are missing due to lack of sys-proctable, so I'm going to close this. It's probably best if you create a module to install the gem (using the "puppet_gem" package provider) and any custom facts that rely on the gem. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481204.1675855391000.10332.1676410500019%40Atlassian.JIRA.
Jira (FACT-3178) Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC
Title: Message Title Josh Cooper updated an issue Facter / FACT-3178 Facter `` ldom.domainrole.impl`` fails on Solaris 11, SPARC Change By: Josh Cooper Component/s: Facter 4 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.479125.1673888594000.10341.1676411100193%40Atlassian.JIRA.
Jira (PUP-11726) Allow Puppet function calls from hiera data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11726 Allow Puppet function calls from hiera data Change By: Josh Cooper Epic Link: PUP-11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.478042.1673279887000.10353.1676411400308%40Atlassian.JIRA.
Jira (FACT-3136) Bug in gce.project.attributes.sshKeys
Title: Message Title Nick GW commented on FACT-3136 Re: Bug in gce.project.attributes.sshKeys While the ssh-keys key in the gce fact is a blob of all the ssh-keys added to the project, it exceeds puppet's fact_value_length_soft_limit configuration setting. This throws a warning on every puppet run. Reverting the change back to facter 3's behavior will resolve this. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.454867.1657650158000.10260.1676400480071%40Atlassian.JIRA.
Jira (FACT-3136) Bug in gce.project.attributes.sshKeys
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3136
Bug in gce.project.attributes.sshKeys
Change By:
Josh Cooper
As a result of running tests against OSs on GCE, it looks like we've found a bug with what the fact gce.project.attributes.sshKeys returned in Facter 3 vs Facter 4: {code:shell}"gce.project.attributes.sshKeys": { "new_value": "jake_spain:ssh-rsa B3NzaC1yc2EDAQABAAABAQClej1oUIbQhSW54TbZ22Q0fFqf50oouD8ktXxsEN0LlzfyDEa9GTjroygsjqo/OWNB/pnQWW4E7pzS2BwjLR9jStVq0LiKuAx/X+Wv9b2+AjPxUiJYyUn6vznzgnWg3CPzVIXXrN7DMld5VPadGPPWc0HDq1AhO6VwxeHXDCAcqeSDXN9j/Kwp0yRX2YywxU/qRRXwpkxeKPVxNsCmBXiHKZK5tEQ1BPUFofhuEBRcXanQ2H9BthHeJ1Le4dPLNeg+t7yAlT6lmnnQXMwfLfaOroda5aXC8wnetaLtwSwtPCG7NRG5t9q63OFSNs+vLJTvG5IeZQkzKauYnC9ifYDr google-ssh {\"userName\":\"jake.sp...@puppet.com\",\"expireOn\":\"2022-03-16T11:58:59+\"}\njake_spain:ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBFqA2Q5PoYwLJBEUiCaICmaGBX7GPdEAbvXFIcYmr6gVydtBErAw2mkYGqlG38vr5vZlQGhB3QeifYvO8YsybAg= google-ssh {\"userName\":\"jake.sp...@puppet.com\",\"expireOn\":\"2022-03-16T11:58:59+\"}\n", "old_value": ["jake_spain:ssh-rsa B3NzaC1yc2EDAQABAAABAQClej1oUIbQhSW54TbZ22Q0fFqf50oouD8ktXxsEN0LlzfyDEa9GTjroygsjqo/OWNB/pnQWW4E7pzS2BwjLR9jStVq0LiKuAx/X+Wv9b2+AjPxUiJYyUn6vznzgnWg3CPzVIXXrN7DMld5VPadGPPWc0HDq1AhO6VwxeHXDCAcqeSDXN9j/Kwp0yRX2YywxU/qRRXwpkxeKPVxNsCmBXiHKZK5tEQ1BPUFofhuEBRcXanQ2H9BthHeJ1Le4dPLNeg+t7yAlT6lmnnQXMwfLfaOroda5aXC8wnetaLtwSwtPCG7NRG5t9q63OFSNs+vLJTvG5IeZQkzKauYnC9ifYDr google-ssh {\"userName\":\"jake.sp...@puppet.com\",\"expireOn\":\"2022-03-16T11:58:59+\"}","jake_spain:ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBFqA2Q5PoYwLJBEUiCaICmaGBX7GPdEAbvXFIcYmr6gVydtBErAw2mkYGqlG38vr5vZlQGhB3QeifYvO8YsybAg= google-ssh {\"userName\":\"jake.sp...@puppet.com\",\"expireOn\":\"2022-03-16T11:58:59+\"}" ]}, {code} Facter 3 parsed the gce data as follows https://github.com/puppetlabs/facter/blob/6d7ffc6efdfbc3b1fc79311cdeb4581ac2098d9c/lib/src/facts/resolvers/gce_resolver.cc#L93-L119 Facter 4 doesn't
Add Comment
Jira (PUP-11755) each/map/filter functions are slow/buggy on jruby
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11755 each/map/filter functions are slow/buggy on jruby Change By: Josh Cooper Fix Version/s: PUP 7.24.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481178.167581186.10302.1676405040077%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Diana Scannicchio created an issue Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Issue Type: Bug Affects Versions: FACT 4.2.13 Assignee: Unassigned Components: Facter 4 Created: 2023/02/14 7:01 AM Fix Versions: FACT 4.2.13 Priority: Normal Reporter: Diana Scannicchio Dear all, we do run "puppet apply" on diskless nodes and in moving to Puppet 7.20 and therefore facter 4.2.13 we noticed a possible bug executing "facter" that appears only on diskless nodes where there is no partition. I tried multiple time to report that issue in December 2022, but Jira did not allow so far to create an account. [my_hostname] facter partitions [2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass It seems the code in /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/facts/linux/partitions.rb does not foreseen to have a diskless node so an empty lis (line 18). It would be nice to have this addressed, not to get the following error from hundreds nodes Error: Facter: undefined method `[]' for nil:NilClass Thank you and best regards, Diana Scannicchio CERN ATLAS TDAQ SysAdmin
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Pat Riehecky created an issue Puppet / PUP-11759 trusted fqdn fact Issue Type: New Feature Assignee: Unassigned Created: 2023/02/14 12:11 PM Priority: Normal Reporter: Pat Riehecky With the legacy top level facts going away, it would be handy if there as a $::trusted['fqdn'] fact I could pull in. In practice I know I can concat $::trusted['hostname'] with $::trusted['domain'], but making sure my mass find/replace is syntax valid for all the quoting and whatnot is going to be ugly. A trusted replacement fact would be great so I don't have to constantly repeat that pattern everywhere. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11751) Unexpected behavior after setting strict to :error
Title: Message Title
Tony Vu updated an issue
Puppet / PUP-11751
Unexpected behavior after setting strict to :error
Change By:
Tony Vu
This ticket is a placeholder for all the unexpected behavior I found while working on PUP-11725 after setting strict to default to {{:error}} instead of {{:warning}} # When rich_data is enabled, users should be able to create and use their own rich data type derived from `Object`.However, [this test|https://github.com/puppetlabs/puppet/blob/f4fbaaac5b21731929e76a7218b3f735ef41cd15/spec/integration/application/apply_spec.rb#L205] that checks Puppet can apply a catalog from an environment with Pcore object types began failing after enabling strict mode. It seems like there was a warning (when strict was set to warning) before that got swallowed and was never noticed. I'll mark the test as pending for now. I also wrote another test that checks that a catalog can be applied without warnings/errors.2. The [lookup function|https://www.puppet.com/docs/puppet/6/function.html#lookup] can take in a {{default_values_hash}} as a parameter and should use that hash to check for the requested key. However, in this [lookup test|https://github.com/puppetlabs/puppet/blob/980a51e3b2e60132c1c00a417b7fc89d353c86f9/spec/unit/functions/lookup_spec.rb#L2414], it fails and does not use the passed in {{default_values_hash}} unless another {{lookup}} is used like [this test|https://github.com/puppetlabs/puppet/blob/980a51e3b2e60132c1c00a417b7fc89d353c86f9/spec/unit/functions/lookup_spec.rb#L2410] does.3. Dig more into this loaders_spec.rb [test|https://github.com/puppetlabs/puppet/blob/fa0250e7338fe156831599d2280339003b46ccc8/spec/unit/pops/loaders/loaders_spec.rb#L248-L251] that checks that a loader can load a function twice when loading from module. For now, I'll mark that test as pending. 4. This [acceptance test|https://github.com/puppetlabs/puppet/blob/25a86b1/acceptance/tests/lookup/config5_interpolation.rb] was also failing in a strange way; `strict` errors caused the test to error out, but without it, the test completes correctly, indicating that `::roles` ends up not actually being undefined.
Add Comment
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11759 trusted fqdn fact Change By: Josh Cooper Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481383.1676405519000.10318.167640998%40Atlassian.JIRA.
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Josh Cooper commented on PUP-11759 Re: trusted fqdn fact Hi Pat Riehecky I wasn't clear if you wanted to use the structured fact "$facts['networking']['fqdn']" which already exists. Or if you are explicitly wanting a trusted version? If so, you can use "$trusted['certname']" which defaults to the fqdn of the host, but doesn't have to be in cases where "certname" is set explicitly in puppet.conf. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481383.1676405519000.10317.167640934%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Josh Cooper updated an issue Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Change By: Josh Cooper Labels: needs-validation regression Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481372.1676386915000.10322.1676409180133%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Josh Cooper updated an issue Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Change By: Josh Cooper Labels: regression Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481372.1676386915000.10321.1676409180089%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3186
facter 4.2.13: bug "facter partitions"
Change By:
Josh Cooper
Dear all,we do run "puppet apply" on diskless nodes and in moving to Puppet 7.20 and therefore facter 4.2.13 we noticed a possible bug executing "facter" that appears only on diskless nodes where there is no partition.I tried multiple time to report that issue in December 2022, but Jira did not allow so far to create an account. {noformat} [my_hostname] facter partitions [2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass {noformat} It seems the code in/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/facts/linux/partitions.rbdoes not foreseen to have a diskless node so an empty lis (line 18).It would be nice to have this addressed, not to get the following error from hundreds nodes {noformat} Error: Facter: undefined method `[]' for nil:NilClass {noformat} Thank you and best regards,Diana ScannicchioCERN ATLAS TDAQ SysAdmin
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3186
facter 4.2.13: bug "facter partitions"
Change By:
Josh Cooper
Dear all,we do run "puppet apply" on diskless nodes and in moving to Puppet 7.20 and therefore facter 4.2.13 we noticed a possible bug executing "facter" that appears only on diskless nodes where there is no partition.I tried multiple time to report that issue in December 2022, but Jira did not allow so far to create an account.{noformat}[my_hostname] facter partitions[2022-12-01 08:49:13.828011 ] ERROR Facter::InternalFactManager - undefined method `[]' for nil:NilClass{noformat}It seems the code in https: / opt / github.com/ puppetlabs/ puppet facter / lib blob / ruby 7eb6e268f2b6e317d0ea35ceff642c3986d6019b / vendor_ruby lib /facter/facts/linux/partitions.rb #L18 does not foreseen to have a diskless node so an empty lis (line 18).It would be nice to have this addressed, not to get the following error from hundreds nodes{noformat}Error: Facter: undefined method `[]' for nil:NilClass{noformat} Thank you and best regards,Diana ScannicchioCERN ATLAS TDAQ SysAdmin
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11759) trusted fqdn fact
Title: Message Title Pat Riehecky commented on PUP-11759 Re: trusted fqdn fact I'd prefer a "fully" trusted version. My certname for the hosts is often a UUID for "reasons" so I'm assembling it by hand with a trivial join. I'm controlling access to SSL certificates and kerberos keytabs, so I don't really want to trust that the client has the right fqdn. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481383.1676405519000.10325.1676409360042%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Josh Cooper updated an issue Facter / FACT-3186 facter 4.2.13: bug "facter partitions" Change By: Josh Cooper Epic Link: PUP-11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481372.1676386915000.10327.1676409360112%40Atlassian.JIRA.
Jira (FACT-3186) facter 4.2.13: bug "facter partitions"
Title: Message Title Josh Cooper commented on FACT-3186 Re: facter 4.2.13: bug "facter partitions" Diana Scannicchio could you confirm that you migrated from Puppet 6.x (facter 3.x) to Puppet 7.20? We'd like to understand how facter was handling this situation before. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481372.1676386915000.10326.1676409360062%40Atlassian.JIRA.
Jira (FACT-3185) facter os.windows.product_name incorrect value for Windows 11
Title: Message Title Josh Cooper updated an issue Facter / FACT-3185 facter os.windows.product_name incorrect value for Windows 11 Change By: Josh Cooper Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.481300.1676300202000.10329.1676409600027%40Atlassian.JIRA.
