Jira (PDB-5548) Partition GC's query bulldozer not guaranteed to make progress
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-5548 Partition GC's query bulldozer not guaranteed to make progress Change By: Rob Browning Assignee: Rob Browning 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.470479.1664997895000.53591.1666937400062%40Atlassian.JIRA.
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title
Georgi Georgiev updated an issue
Facter / FACT-3165
facter --debug reports wrong location of a resolved fact.
Change By:
Georgi Georgiev
When a fact is defined in multiple files, running `facter --debug` reports the wrong location it was resolved from.Steps to reproduce: {{ {{$ grep '' *}} }} {{ {}{{ one.rb:Facter.add("foo") { setcode{ do }} } {{ { one.rb: setcode do } } { {one.rb: "one" } { } }} {{ { one.rb: end }} }} { {one.rb:end }} } {{ {}{{ zero.rb:Facter.add("foo") { setcode{ do }} } {{ { zero.rb: setcode do } } { {zero.rb: "zero" } { } }} {{ { zero.rb: end }} }} { {zero.rb:end }} } {} $ facter foo --debug --custom-dir $PWD 2>&1 | grep -e zero -e one { } {} [2022-10-28 10:45:17.906705 ] DEBUG Facter::Util::Fact - custom fact foo got resolved from: ["/tmp/x/{color:#ff}*zero*{color}.rb", 1] { } {} [2022-10-28 10:45:17.907721 ] DEBUG Facter::FactManager - fact "foo" has resolved to: *{color:#ff8b00}one{color}* { } {{*{color:#ff8b00}{{one}}{color}*}}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title
Georgi Georgiev updated an issue
Facter / FACT-3165
facter --debug reports wrong location of a resolved fact.
Change By:
Georgi Georgiev
When a fact is defined in multiple files, running `facter --debug` reports the wrong location it was resolved from.Steps to reproduce: {{grep '' *}}{{one.rb:Facter.add("foo") do}}{{one.rb: setcode do}}{{one.rb: "one"}}{{one.rb: end}}{{one.rb:end}}{{zero.rb:Facter.add("foo") do}}{{zero.rb: setcode do}}{{zero.rb: "zero"}}{{zero.rb: end}}{{zero.rb:end}}{{ {{{} $ facter foo --debug --custom-dir $PWD 2>&1 | grep -e zero -e one { }} }}} {{ {{{} [2022-10-28 10:45:17.906705 ] DEBUG Facter::Util::Fact - custom fact foo got resolved from: ["/tmp/x/{color:#ff}*zero*{color}.rb", 1] { }} }}} {{ {{{} [2022-10-28 10:45:17.907721 ] DEBUG Facter::FactManager - fact "foo" has resolved to: *{color:#ff8b00}one{color}* { }} }}} {{*{color:#ff8b00}{{one}}{color}*}}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title
Georgi Georgiev updated an issue
Facter / FACT-3165
facter --debug reports wrong location of a resolved fact.
Change By:
Georgi Georgiev
When a fact is defined in multiple files, running `facter --debug` reports the wrong location it was resolved from.Steps to reproduce: {{ $ grep '' *}}{{one.rb:Facter.add("foo") do}}{{one.rb: setcode do}}{{one.rb: "one"}}{{one.rb: end}}{{one.rb:end}}{{zero.rb:Facter.add("foo") do}}{{zero.rb: setcode do}}{{zero.rb: "zero"}}{{zero.rb: end}}{{zero.rb:end}}{{$ facter foo --debug --custom-dir $PWD 2>&1 | grep -e zero -e one}}{{[2022-10-28 10:45:17.906705 ] DEBUG Facter::Util::Fact - custom fact foo got resolved from: ["/tmp/x/{color:#ff}*zero*{color}.rb", 1]}}{{[2022-10-28 10:45:17.907721 ] DEBUG Facter::FactManager - fact "foo" has resolved to: *{color:#ff8b00}one{color}*}}{{*{color:#ff8b00}{{one}}{color}*}}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message be
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title
Georgi Georgiev updated an issue
Facter / FACT-3165
facter --debug reports wrong location of a resolved fact.
Change By:
Georgi Georgiev
When a fact is defined in multiple files, running `facter --debug` reports the wrong location it was resolved from.Steps to reproduce: {{ {{ $ grep '' *}} }} {{ {}{{ one.rb:Facter.add("foo") \ { setcode { }}}{{{}{ "one" } { }}} {{{{}}} {{ {}{{ zero.rb:Facter.add("foo") \ { setcode { }}}{{{}{ "zero" } { }}} {{{{}}} {{ {{ $ facter foo --debug --custom-dir $PWD 2>&1 | grep -e zero -e one}} }} {{ {{ [2022-10-28 10:45:17.906705 ] DEBUG Facter::Util::Fact - custom fact foo got resolved from: ["/tmp/x/{color:# FF ff }*zero*{color}.rb", 1]}} }} {{ {{ [2022-10-28 10:45:17.907721 ] DEBUG Facter::FactManager - fact "foo" has resolved to: *{color:#ff8b00}one{color}*}} }} {{ *{color:#ff8b00}{{one}}{color}* }}
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
You received this message because you are subscribe
Jira (FACT-3165) facter --debug reports wrong location of a resolved fact.
Title: Message Title Georgi Georgiev created an issue Facter / FACT-3165 facter --debug reports wrong location of a resolved fact. Issue Type: Bug Affects Versions: FACT 4.2.11 Assignee: Unassigned Components: Facter 4 Created: 2022/10/27 6:47 PM Environment: $ facter --version 4.2.11 $ rpm -qf $(which facter) -i Name : puppet-agent Version : 7.18.0 Release : 1.el8 Architecture: x86_64 Install Date: Mon 03 Oct 2022 10:40:53 AM JST Group : System Environment/Base Size : 112577683 License : See components Signature : RSA/SHA256, Sat 23 Jul 2022 01:48:23 AM JST, Key ID 4528b6cd9e61ef26 Source RPM : puppet-agent-7.18.0-1.el8.src.rpm Build Date : Sat 23 Jul 2022 01:47:31 AM JST Build Host : unheated-luck.delivery.puppetlabs.net Relocations : (not relocatable) Vendor : Puppet Labs URL : https://www.puppetlabs.com Summary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, and hiera. Description : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, and hiera.Contains the following components: cleanup facter 4.2.11 hiera 3.10.0 module-puppetlabs-augeas_core 1.1.2 module-puppetlabs-cron_core 1.0.5 module-puppetlabs-host_core 1.0.3 module-puppetlabs-mount_core 1.0.4 module-puppetlabs-scheduled_task 1.0.0 module-puppetlabs-selinux_core 1.1.0 module-puppetlabs-sshkeys_core 2.2.0 module-puppetlabs-yumrepo_core 1.0.7 module-puppetlabs-zfs_core 1.2.0 module-puppetlabs-zone_core 1.0.3 pl-ruby-patch puppet 7.18.0 puppet-resource_api 1.8.14 puppet-runtime 202207190 pxp-agent 202207200 shellpath 2015-09-18 wrapper-script Priority: Low Reporter: Georgi Georgiev
Jira (PUP-11665) 16. Update Public-facing Puppet docs to include macOS 13 (ARM)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11665 16. Update Public-facing Puppet docs to include macOS 13 (ARM) Change By: Josh Cooper Epic Link: PA-4773 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.473598.1666905087000.53509.1666905120170%40Atlassian.JIRA.
Jira (PUP-11665) 16. Update Public-facing Puppet docs to include macOS 13 (ARM)
Title: Message Title Josh Cooper created an issue Puppet / PUP-11665 16. Update Public-facing Puppet docs to include macOS 13 (ARM) Issue Type: Task Assignee: Unassigned Created: 2022/10/27 2:11 PM Labels: os Priority: Normal Reporter: Josh Cooper See https://confluence.puppetlabs.com/display/AGENT/How+to+add+a+platform+for+puppet-agent#Howtoaddaplatformforpuppetagent-update_public_facing_docs Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11527) puppet lookup -E doesn't execute the ENC
Title: Message Title Aria Li assigned an issue to Unassigned Puppet / PUP-11527 puppet lookup -E doesn't execute the ENC Change By: Aria Li Assignee: Aria Li 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.446077.1651506969000.53480.1666901160035%40Atlassian.JIRA.
Jira (PUP-11631) Purging SSH keys on a user resource fails when alias is used
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-11631 Purging SSH keys on a user resource fails when alias is used Change By: Michael Hashizume Assignee: Michael Hashizume 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.469398.1663952875000.53446.1666897920205%40Atlassian.JIRA.
Jira (PUP-11527) puppet lookup -E doesn't execute the ENC
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11527 puppet lookup -E doesn't execute the ENC Change By: Josh Cooper Acceptance Criteria: It should be possible to set a node parameter in an external node classifier, reference that node parameter in hiera.yaml and ensure the value is resolved correctly when running "puppet lookup -E " for the current node, for a different node and with/without the --compile option. If "-E" is omitted, then it should default to the environment specified in puppet.conf or default to "production"By default, it should be possible to interpolate the "environment" parameter in hiera. However, if an explicit environment is specified (via -E) then it should take precedence over what the ENC returned. 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.446077.1651506969000.53431.1666895400047%40Atlassian.JIRA.
Jira (PUP-11527) puppet lookup -E doesn't execute the ENC
Title: Message Title Aria Li assigned an issue to Aria Li Puppet / PUP-11527 puppet lookup -E doesn't execute the ENC Change By: Aria Li Assignee: Aria Li 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.446077.1651506969000.53427.1666894860032%40Atlassian.JIRA.
Jira (PUP-11527) puppet lookup -E doesn't execute the ENC
Title: Message Title Aria Li assigned an issue to Unassigned Puppet / PUP-11527 puppet lookup -E doesn't execute the ENC Change By: Aria Li Assignee: Aria Li 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.446077.1651506969000.53413.1666894260033%40Atlassian.JIRA.
Jira (PUP-10688) tidy resource does not honor schedule metaparameter
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10688 tidy resource does not honor schedule metaparameter Change By: Josh Cooper Sprint: Phoenix 2022-11-23 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.374080.1602010849000.53350.1666889820044%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Josh Cooper commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent We attempted to disable legacy facts many years ago by blocking them in facter. However, that breaks types and providers that confine/defaultfor based on legacy facts, like the builtin "init" service provider: $ puppet apply -e '' Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass In order to disable legacy facts without breaking agents and provide a graceful migration path, we need to handle this in puppet, not facter. I've filed PUP-11662, which will make it possible to disable legacy facts in puppet 7.x. In puppet 8, we will fix puppet's builtin types/providers to reference structured facts and disable legacy facts by default (PUP-11430). Therefore, I'm going to close this as a duplicate, superseded by the puppet tickets. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11662) Allow legacy facts to be excluded
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11662 Allow legacy facts to be excluded Change By: Josh Cooper Acceptance Criteria: By default there should be no change in how the agent collects or sends facts (legacy, core, external or custom)If legacy facts are disabled, then the agent should not send legacy facts. However, types and providers that confine or set defaultsfor based on legacy facts should still work. Also custom and external facts should continue to be sent. 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.472752.1666307268000.53286.1666885980060%40Atlassian.JIRA.
