Jira (PUP-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider
Title: Message Title Josh Cooper commented on PUP-6552 Re: Regression: Redhat / Debian / Ubuntu can't specify 'init' provider Moved to Open for triage. Is this still an issue? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.143641.1469570086000.38539.1586920440038%40Atlassian.JIRA.
Jira (FACT-2554) Distro-packaged facter (3.14.2) on Fedora 31 segfault on external fact from .yaml
Title: Message Title bbradley created an issue Facter / FACT-2554 Distro-packaged facter (3.14.2) on Fedora 31 segfault on external fact from .yaml Issue Type: Bug Assignee: Unassigned Attachments: facter_f31_barf.txt Created: 2020/04/14 6:01 PM Environment: Stock Fedora 31 install with distro-provided versions of facter, puppet and ruby... root@saltmaster01:0 ~ # uname -a Linux saltmaster01.int 5.5.15-200.fc31.x86_64 #1 SMP Thu Apr 2 19:16:17 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@saltmaster01:0 ~ # dnf list installed | grep fact facter.x86_643.14.2-1.fc31 @fedora ruby-facter.x86_64 3.14.2-1.fc31 @fedora root@saltmaster01:0 ~ # dnf list installed | grep puppet
Jira (PDOC-301) Docs Process Improvements
Title: Message Title Jesse Scott moved an issue Puppet Strings / PDOC-301 Docs Process Improvements Change By: Jesse Scott Key: PUP PDOC - 9425 301 Project: Puppet Strings Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.291456.1547157877000.38407.1586907540073%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-10364 Add new ppRegCertExt OID "pp_owner" Change By: Reid Vandewiele Release Notes: Enhancement Release Notes Summary: Provide a new certificate extension OID and short-name, pp_owner Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38307.1586901420032%40Atlassian.JIRA.
Jira (BOLT-1545) ERROR Facter::ClassDiscoverer - There is no module named Ol
Title: Message Title Robert Sabo Sipos created an issue Puppet Task Runner / BOLT-1545 ERROR Facter::ClassDiscoverer - There is no module named Ol Issue Type: Bug Assignee: Unassigned Components: bolt Created: 2020/04/14 1:48 PM Priority: Normal Reporter: Robert Sabo Sipos Bolt Version: 2.4.0 (also present in 2.5.0) OS Name/Version: Oracle Linux 7.x The following error has started showing up since the upgrade to Bolt 2.4.0 when trying to list tasks (bolt task show) or plans (bolt plan show) on an Oracle Linux server: ERROR Facter::ClassDiscoverer - There is no module named Ol The same error shows up in the command output when running any Bolt tasks (bolt task run) or plans (bolt plan run). It does NOT happen when running regular shell commands (bolt command run). The same error is still present in the currently latest Bolt version 2.5.0 Steps to reproduce: $ bolt task show [2020-04-14 20:34:52.258500 ] ERROR Facter::ClassDiscoverer - There is no module named Ol Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Could not autoload puppet/provider/service/freebsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass $ bolt plan show [2020-04-14 20:35:58.686674 ] ERROR Facter::ClassDiscoverer - There is no module named Ol Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Could not autoload puppet/provider/service/freebsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Desired Behavior: Bolt tasks and plans executing without an error on Oracle Linux. Actual Behavior: Bolt task and plan command output is showing "Facter::ClassDiscoverer - There is no module named Ol" error on Oracle Linux.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10364 Add new ppRegCertExt OID "pp_owner" Change By: Justin Stoller Fix Version/s: SERVER 6.10.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38195.1586896800028%40Atlassian.JIRA.
Jira (PUP-10395) Gem provider reports changes when using composed requirements
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10395 Gem provider reports changes when using composed requirements Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.351406.1585318227000.38182.1586896620028%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Josh Cooper commented on PUP-10364 Re: Add new ppRegCertExt OID "pp_owner" Passed CI awhile ago, but most recently 1207443715. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38180.1586896560087%40Atlassian.JIRA.
Jira (PUP-8051) puppet agent option to wait for lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8051 puppet agent option to wait for lock Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.216234.1507933383000.38181.1586896560131%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10364 Add new ppRegCertExt OID "pp_owner" Change By: Josh Cooper Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38177.1586896500107%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Josh Cooper commented on PUP-10364 Re: Add new ppRegCertExt OID "pp_owner" Reid Vandewiele can you update the release notes tab? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38178.1586896500151%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Josh Cooper commented on PUP-10364 Re: Add new ppRegCertExt OID "pp_owner" Merged to puppet#master in https://github.com/puppetlabs/puppet/commit/c2600626a56c41ec4e89352d8c4ba41fc9bd1e08. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38176.1586896500053%40Atlassian.JIRA.
Jira (PUP-10364) Add new ppRegCertExt OID "pp_owner"
Title: Message Title Justin Stoller commented on PUP-10364 Re: Add new ppRegCertExt OID "pp_owner" It looks like this landed in Puppet, Puppet Server, & the ca cli? Can Reid Vandewiele or Josh Cooper confirm? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349188.1583867523000.38159.1586895720135%40Atlassian.JIRA.
Jira (FACT-2390) make facter 2x recursion check thread-safe
Title: Message Title Justin Stoller commented on FACT-2390 Re: make facter 2x recursion check thread-safe Maggie's comment was with reference to our dev env, but for posterity the Server 6.10.0 release will be the first release that was tested with Facter 2.5.8. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.347008.1582157687000.38154.1586895420026%40Atlassian.JIRA.
Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10420 Observe waitforlock when acquiring the ssl lock Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355521.1586889868000.38048.1586890020029%40Atlassian.JIRA.
Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10420 Observe waitforlock when acquiring the ssl lock Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355521.1586889868000.38047.1586889960070%40Atlassian.JIRA.
Jira (PUP-10420) Observe waitforlock when acquiring the ssl lock
Title: Message Title Josh Cooper created an issue Puppet / PUP-10420 Observe waitforlock when acquiring the ssl lock Issue Type: Bug Assignee: Unassigned Created: 2020/04/14 11:44 AM Fix Versions: PUP 6.15.0 Priority: Normal Reporter: Josh Cooper PUP-8051 adds an option so the agent can wait for an in-progress run to finish. This ticket is to add the same functionality to the ssl state machine lock. This ticket is blocked on which is blocked on PUP-10228 Add Comment This message was sent by
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Justin Stoller commented on PUP-10417 Re: Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Thanks, Henrik! Based on that I would say that this should be a documentation ticket that additional helper methods should all live inside the body of the block passed to create_function and the be made a documentation ticket. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354928.1586391583000.38019.1586888400030%40Atlassian.JIRA.
Jira (PUP-10371) Add metric for Puppet Agent run
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10371 Add metric for Puppet Agent run Change By: Melissa Stone Fix Version/s: PUP 6.15.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349708.1584344056000.38014.1586887860096%40Atlassian.JIRA.
Jira (PUP-10371) Add metric for Puppet Agent run
Title: Message Title Melissa Stone commented on PUP-10371 Re: Add metric for Puppet Agent run This has been merged into master with https://github.com/puppetlabs/puppet/commit/da802790ac062984d200d29f321a7de575ce8aba Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.349708.1584344056000.38013.1586887860041%40Atlassian.JIRA.
Jira (FACT-2553) Backslashes are handled differently in facter-ng
Title: Message Title Josh Cooper created an issue Facter / FACT-2553 Backslashes are handled differently in facter-ng Issue Type: Bug Assignee: Unassigned Created: 2020/04/14 10:16 AM Priority: Normal Reporter: Josh Cooper I see two differences when comparing facter and facter-ng output on Windows 2019. The aio_agent_version and puppetversion facts are missing. Also paths with backslashes often are escaped on facter-ng, but not facter: 1d0 < aio_agent_version => 6.14.0.237 10,11c9,10 < env_windows_installdir => C:\Program Files\Puppet Labs\Puppet < facterversion => 3.14.10 --- >
Jira (PDB-4635) puppetdb_avg_mem larger than baseline values
Title: Message Title John Duarte commented on PDB-4635 Re: puppetdb_avg_mem larger than baseline values For the performance comparison run of week 2020-04-013, this tolerance failed when testing recent PE master build (2019.7.0-rc0-49-g5037017) to the LTS baseline (but not STS). 2019.7.0-rc0-49-g5037017 2018.1.13 comparison: Result 'process_puppetdb_avg_mem' is outside tolerances: baseline: 730773; result: 909854; variance: 24.51% Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.343321.1579814655000.37886.1586884020031%40Atlassian.JIRA.
Jira (FACT-2547) undefined method 'debug' for nil:NilClass
Title: Message Title Josh Cooper commented on FACT-2547 Re: undefined method 'debug' for nil:NilClass Thanks, I confirmed it's working, I'll close this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355394.1586802004000.37879.1586883720034%40Atlassian.JIRA.
Jira (PDB-4636) Add migrate configuration option
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4636 Add migrate configuration option Change By: Rob Browning Release Notes Summary: A `[database] migrate ? ` configuration option has been added. When set to `true` (the default), PuppetDB will upgrade the data in the database to the latest format at startup. When `false`, PuppetDB will exit with an error status if the format version is not the one it expects, whether newer or older. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.343741.1580162292000.37768.1586878200065%40Atlassian.JIRA.
Jira (PUP-10416) Comparing rpm package versions without epoch fails
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10416 Comparing rpm package versions without epoch fails Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-04-29 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354829.1586361879000.37702.1586876040042%40Atlassian.JIRA.
Jira (FACT-2537) Not compatible with leatherman >= 1.0.0
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2537 Not compatible with leatherman >= 1.0.0 Change By: Mihai Buzgau Sprint: NW - 2020-04-15 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354200.1586117199000.37695.1586875860120%40Atlassian.JIRA.
Jira (FACT-2537) Not compatible with leatherman >= 1.0.0
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2537 Not compatible with leatherman >= 1.0.0 Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354200.1586117199000.37694.1586875860077%40Atlassian.JIRA.
Jira (PUP-10412) systemd service provider only works on running systems
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10412 systemd service provider only works on running systems Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354201.158612400.37696.1586875860164%40Atlassian.JIRA.
Jira (PUP-10419) Support disable module with dnfmodule package provider
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10419 Support disable module with dnfmodule package provider Change By: Gabriel Nagy Sprint: PR - Triage Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355472.1586866878000.37594.1586867220026%40Atlassian.JIRA.
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Vadym Chepkov commented on PUP-10235 Re: Support enable module with dnfmodule package provider sure, https://tickets.puppetlabs.com/browse/PUP-10419 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342086.157904321.37593.1586866980025%40Atlassian.JIRA.
Jira (PUP-10419) Support disable module with dnfmodule package provider
Title: Message Title Vadym Chepkov created an issue Puppet / PUP-10419 Support disable module with dnfmodule package provider Issue Type: New Feature Assignee: Unassigned Created: 2020/04/14 5:21 AM Priority: Normal Reporter: Vadym Chepkov dnfmodule package provider currently only supports 'enable' operation. disable operation should be added as well, which would allow use alternative sources for the OS packages, not supporting modular design. For example, to install postgresql 11 one needs to disable 'postgresql' module # dnf module list --disabledLast metadata expiration check: 0:01:36 ago on Mon 13 Apr 2020 05:23:56 PM UTC.CentOS-8 - AppStreamName Stream Profiles Summary postgresql 9.6 [x] client, server [d] PostgreSQL server and client module postgresql 10 [d][x] client, server [d] PostgreSQL server and client module postgresql 12 [x] client, server PostgreSQL server and client module Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled
Jira (PUP-10235) Support enable module with dnfmodule package provider
Title: Message Title Gabriel Nagy commented on PUP-10235 Re: Support enable module with dnfmodule package provider Thanks for the additional information, Vadym Chepkov. Would you be able to open a PUP ticket for this functionality? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342086.157904321.37585.1586865720028%40Atlassian.JIRA.
Jira (FACT-2552) Add processors fact for Solaris
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2552 Add processors fact for Solaris Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355470.1586858931000.37524.158685971%40Atlassian.JIRA.
Jira (FACT-2552) Add processors fact for Solaris
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2552 Add processors fact for Solaris Issue Type: Task Assignee: Unassigned Created: 2020/04/14 3:08 AM Priority: Normal Reporter: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2551) Resolver is called multiple times even if the fact cannot be resolved
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2551
Resolver is called multiple times even if the fact cannot be resolved
Change By:
Gheorghe Popescu
This can have major performance implications if the resolver is slow.*Context:*Facter 4 is caching resolver data so that resolvers that are used by multiple facts make the system calls only once.*Issue:*If a fact cannot be retrieved from the system, the resolver is called each time that fact is requested, and all the system calls are done again. *Example:* OS X system_profiler : [https://github.com/puppetlabs/facter-ng/blob/master/lib/resolvers/macosx/system_profiler_resolver.rb#L38] does not have information about `subsystem_vendor_id`OS X is_virtual is calling again for the `subsystem_vendor_id`: [https://github.com/puppetlabs/facter-ng/blob/975344c6a0bdde9bbc208ff6381c00733a48e0c0/lib/facts/macosx/is_virtual.rb#L25] This makes the resolver to make 2 expensive system calls of ~0.4 seconds each(2/3 of total facter run)*Backtrace:*{code:java}❯ bx facter--First Callfact_list: {}fact_name: model_identifier user system totalreal 0.031205 0.021051 0.291823 ( 0.438509)--calling retrieve_system_profiler["facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `block in post_resolve'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `fetch'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `post_resolve'", "facter-ng/lib/resolvers/base_resolver.rb:21:in `block in resolve'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `synchronize'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `resolve'", "facter-ng/lib/facts/macosx/is_virtual.rb:19:in `hypervisor_name'", "facter-ng/lib/facts/macosx/is_virtual.rb:15:in `virtual?'", "facter-ng/lib/facts/macosx/is_virtual.rb:9:in `call_the_resolver'", "facter-ng/lib/framework/core/fact/internal/core_fact.rb:12:in `create'", "facter-ng/lib/framework/core/fact/internal/internal_fact_manager.rb:27:in `block (2 levels) in start_threads'"]--Second Callfact_list: { :model_name=> 'value' :model_identifier=> 'value' :processor_name=> 'value' :processor_speed=> 'value' :number_of_processors=> 'value' :total_number_of_cores=> 'value' :l2_cache_per_core=> 'value' :l3_cache=> 'value' :"hyper-threading_technology"=> 'value' :memory=> 'value' :boot_rom_version=> 'value' :smc_version_system=> 'value' :serial_number_system=> 'value' :hardware_uuid=> 'value' :system_version=> 'value' :kernel_version=> 'value' :boot_volume=> 'value' :boot_mode=> 'value' :computer_name=> 'value' :user_name=> 'value' :secure_virtual_memory=> 'value' :system_integrity_protection=> 'value' :time_since_boot=> 'value'}fact_name: subsystem_vendor_id user system totalreal 0.000297 0.001640 0.209305 ( 0.430579)--calling
Jira (FACT-2551) Resolver is called multiple times even if the fact cannot be resolved
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2551
Resolver is called multiple times even if the fact cannot be resolved
Change By:
Gheorghe Popescu
This can have major performance implications if the resolver is slow.*Context:*Facter 4 is caching resolver data so that resolver resolvers that are used by multiple facts to make the system calls only once.*Issue:*If a fact cannot be retrieved from the system, the resolver is called each time that fact is request, and all the system calls are done again. *Example:* OS X system_profiler : [https://github.com/puppetlabs/facter-ng/blob/master/lib/resolvers/macosx/system_profiler_resolver.rb#L38] does not have information about `subsystem_vendor_id`OS X is_virtual is calling again for the `subsystem_vendor_id`: [https://github.com/puppetlabs/facter-ng/blob/975344c6a0bdde9bbc208ff6381c00733a48e0c0/lib/facts/macosx/is_virtual.rb#L25] This makes the resolver to make 2 expensive system calls of ~0.4 seconds each(2/3 of total facter run)*Backtrace:*{code:java}❯ bx facter--First Callfact_list: {}fact_name: model_identifier user system totalreal 0.031205 0.021051 0.291823 ( 0.438509)--calling retrieve_system_profiler["facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `block in post_resolve'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `fetch'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `post_resolve'", "facter-ng/lib/resolvers/base_resolver.rb:21:in `block in resolve'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `synchronize'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `resolve'", "facter-ng/lib/facts/macosx/is_virtual.rb:19:in `hypervisor_name'", "facter-ng/lib/facts/macosx/is_virtual.rb:15:in `virtual?'", "facter-ng/lib/facts/macosx/is_virtual.rb:9:in `call_the_resolver'", "facter-ng/lib/framework/core/fact/internal/core_fact.rb:12:in `create'", "facter-ng/lib/framework/core/fact/internal/internal_fact_manager.rb:27:in `block (2 levels) in start_threads'"]--Second Callfact_list: { :model_name=> 'value' :model_identifier=> 'value' :processor_name=> 'value' :processor_speed=> 'value' :number_of_processors=> 'value' :total_number_of_cores=> 'value' :l2_cache_per_core=> 'value' :l3_cache=> 'value' :"hyper-threading_technology"=> 'value' :memory=> 'value' :boot_rom_version=> 'value' :smc_version_system=> 'value' :serial_number_system=> 'value' :hardware_uuid=> 'value' :system_version=> 'value' :kernel_version=> 'value' :boot_volume=> 'value' :boot_mode=> 'value' :computer_name=> 'value' :user_name=> 'value' :secure_virtual_memory=> 'value' :system_integrity_protection=> 'value' :time_since_boot=> 'value'}fact_name: subsystem_vendor_id user system totalreal 0.000297 0.001640 0.209305 (
Jira (FACT-2551) Resolver is called multiple times even if the fact cannot be resolved
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2551
Resolver is called multiple times even if the fact cannot be resolved
Change By:
Gheorghe Popescu
This can have major performance implications if the resolver is slow.*Context:*Facter 4 is caching resolver data so that resolvers that are used by multiple facts make the system calls only once.*Issue:*If a fact cannot be retrieved from the system, the resolver is called each time that fact is request requested , and all the system calls are done again. *Example:* OS X system_profiler : [https://github.com/puppetlabs/facter-ng/blob/master/lib/resolvers/macosx/system_profiler_resolver.rb#L38] does not have information about `subsystem_vendor_id`OS X is_virtual is calling again for the `subsystem_vendor_id`: [https://github.com/puppetlabs/facter-ng/blob/975344c6a0bdde9bbc208ff6381c00733a48e0c0/lib/facts/macosx/is_virtual.rb#L25] This makes the resolver to make 2 expensive system calls of ~0.4 seconds each(2/3 of total facter run)*Backtrace:*{code:java}❯ bx facter--First Callfact_list: {}fact_name: model_identifier user system totalreal 0.031205 0.021051 0.291823 ( 0.438509)--calling retrieve_system_profiler["facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `block in post_resolve'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `fetch'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `post_resolve'", "facter-ng/lib/resolvers/base_resolver.rb:21:in `block in resolve'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `synchronize'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `resolve'", "facter-ng/lib/facts/macosx/is_virtual.rb:19:in `hypervisor_name'", "facter-ng/lib/facts/macosx/is_virtual.rb:15:in `virtual?'", "facter-ng/lib/facts/macosx/is_virtual.rb:9:in `call_the_resolver'", "facter-ng/lib/framework/core/fact/internal/core_fact.rb:12:in `create'", "facter-ng/lib/framework/core/fact/internal/internal_fact_manager.rb:27:in `block (2 levels) in start_threads'"]--Second Callfact_list: { :model_name=> 'value' :model_identifier=> 'value' :processor_name=> 'value' :processor_speed=> 'value' :number_of_processors=> 'value' :total_number_of_cores=> 'value' :l2_cache_per_core=> 'value' :l3_cache=> 'value' :"hyper-threading_technology"=> 'value' :memory=> 'value' :boot_rom_version=> 'value' :smc_version_system=> 'value' :serial_number_system=> 'value' :hardware_uuid=> 'value' :system_version=> 'value' :kernel_version=> 'value' :boot_volume=> 'value' :boot_mode=> 'value' :computer_name=> 'value' :user_name=> 'value' :secure_virtual_memory=> 'value' :system_integrity_protection=> 'value' :time_since_boot=> 'value'}fact_name: subsystem_vendor_id user system totalreal 0.000297 0.001640 0.209305 (
Jira (FACT-2551) Resolver is called multiple times even if the fact cannot be resolved
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2551
Resolver is called multiple times even if the fact cannot be resolved
Change By:
Gheorghe Popescu
This can have major performance implications if the resolver is slow. * Context: * Facter 4 is caching resolver data so that resolver that are used by multiple facts to make the system calls only once. * Issue: * If a fact cannot be retrieved from the system, the resolver is called each time that fact is request, and all the system calls are done again. * Example: * OS X system_profiler : [https://github.com/puppetlabs/facter-ng/blob/master/lib/resolvers/macosx/system_profiler_resolver.rb#L38] does not have information about `subsystem_vendor_id`OS X is_virtual is calling again for the `subsystem_vendor_id`: [https://github.com/puppetlabs/facter-ng/blob/975344c6a0bdde9bbc208ff6381c00733a48e0c0/lib/facts/macosx/is_virtual.rb#L25] This makes the resolver to make 2 expensive system calls of ~0.4 seconds each(2/3 of total facter run) * Backtrace: * {code:java}❯ bx facter--First Callfact_list: {}fact_name: model_identifier user system totalreal 0.031205 0.021051 0.291823 ( 0.438509)--calling retrieve_system_profiler["facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `block in post_resolve'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `fetch'", "facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:40:in `post_resolve'", "facter-ng/lib/resolvers/base_resolver.rb:21:in `block in resolve'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `synchronize'", "facter-ng/lib/resolvers/base_resolver.rb:19:in `resolve'", "facter-ng/lib/facts/macosx/is_virtual.rb:19:in `hypervisor_name'", "facter-ng/lib/facts/macosx/is_virtual.rb:15:in `virtual?'", "facter-ng/lib/facts/macosx/is_virtual.rb:9:in `call_the_resolver'", "facter-ng/lib/framework/core/fact/internal/core_fact.rb:12:in `create'", "facter-ng/lib/framework/core/fact/internal/internal_fact_manager.rb:27:in `block (2 levels) in start_threads'"]--Second Callfact_list: { :model_name=> 'value' :model_identifier=> 'value' :processor_name=> 'value' :processor_speed=> 'value' :number_of_processors=> 'value' :total_number_of_cores=> 'value' :l2_cache_per_core=> 'value' :l3_cache=> 'value' :"hyper-threading_technology"=> 'value' :memory=> 'value' :boot_rom_version=> 'value' :smc_version_system=> 'value' :serial_number_system=> 'value' :hardware_uuid=> 'value' :system_version=> 'value' :kernel_version=> 'value' :boot_volume=> 'value' :boot_mode=> 'value' :computer_name=> 'value' :user_name=> 'value' :secure_virtual_memory=> 'value' :system_integrity_protection=> 'value' :time_since_boot=> 'value'}fact_name: subsystem_vendor_id user system totalreal 0.000297 0.001640 0.209305 (
Jira (FACT-2551) Resolver is called multiple times even if the fact cannot be resolved
Title: Message Title
Gheorghe Popescu created an issue
Facter / FACT-2551
Resolver is called multiple times even if the fact cannot be resolved
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2020/04/14 2:23 AM
Priority:
Normal
Reporter:
Gheorghe Popescu
This can have major performance implications if the resolver is slow. Context: Facter 4 is caching resolver data so that resolver that are used by multiple facts to make the system calls only once. Issue: If a fact cannot be retrieved from the system, the resolver is called each time that fact is request, and all the system calls are done again. Example: OS X system_profiler : https://github.com/puppetlabs/facter-ng/blob/master/lib/resolvers/macosx/system_profiler_resolver.rb#L38 does not have information about `subsystem_vendor_id` OS X is_virtual is calling again for the `subsystem_vendor_id`: https://github.com/puppetlabs/facter-ng/blob/975344c6a0bdde9bbc208ff6381c00733a48e0c0/lib/facts/macosx/is_virtual.rb#L25 This makes the resolver to make 2 expensive system calls of ~0.4 seconds each(2/3 of total facter run) Backtrace:
❯ bx facter--First Call
fact_list: {}
fact_name: model_identifier
Jira (FACT-2550) Fix logger tests for FileHelper wrapper
Title: Message Title Andrei Filipovici updated an issue Facter / FACT-2550 Fix logger tests for FileHelper wrapper Change By: Andrei Filipovici Epic Link: FACT-2458 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355448.1586847019000.37441.1586853240035%40Atlassian.JIRA.
Jira (FACT-2547) undefined method 'debug' for nil:NilClass
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2547 undefined method 'debug' for nil:NilClass Change By: Oana Tanasoiu Sub-team: ghost Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355394.1586802004000.37412.1586847600182%40Atlassian.JIRA.
Jira (FACT-2547) undefined method 'debug' for nil:NilClass
Title: Message Title Bogdan Irimie assigned an issue to Sebastian Miclea Facter / FACT-2547 undefined method 'debug' for nil:NilClass Change By: Bogdan Irimie Assignee: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355394.1586802004000.37411.1586847480030%40Atlassian.JIRA.
Jira (FACT-2547) undefined method 'debug' for nil:NilClass
Title: Message Title Bogdan Irimie commented on FACT-2547 Re: undefined method 'debug' for nil:NilClass Hi Josh, the issue was caused by a logger that was not instantiated at the appropriate moment. A fix was already merged https://github.com/puppetlabs/facter-ng/pull/447/files Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355394.1586802004000.37410.1586847360084%40Atlassian.JIRA.
Jira (FACT-2550) Fix logger tests for FileHelper wrapper
Title: Message Title Andrei Filipovici created an issue Facter / FACT-2550 Fix logger tests for FileHelper wrapper Issue Type: Bug Assignee: Andrei Filipovici Created: 2020/04/13 11:50 PM Priority: Normal Reporter: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2549) POC Facts for OS are configured in config file
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2549 POC Facts for OS are configured in config file Change By: Bogdan Irimie Epic Link: FACT-2109 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.355446.1586843892000.37407.158684429%40Atlassian.JIRA.
Jira (FACT-2549) POC Facts for OS are configured in config file
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2549 POC Facts for OS are configured in config file Issue Type: Task Assignee: Unassigned Created: 2020/04/13 10:58 PM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
