Jira (FACT-2513) command line help does flags incorrectly
Title: Message Title
Jesse Reynolds updated an issue
Facter / FACT-2513
command line help does flags incorrectly
Change By:
Jesse Reynolds
Running {{facter _facter - h}} h_ to get online help shows single letter command line options (flags) without the preceding dash {{ _ - }} _ . Eg {{f}} _f_ instead of {{ _ - f}} f_ {noformat}~ $ facter -hCommands: facter --list-block-groups # List block groups facter [options] [query] [query] [...] # facter help [COMMAND] # Describe available commands or one specific commandOptions: [--color], [--no-color] # Enable color output. c, [--config=CONFIG] # The location of the config file. [--custom-dir=CUSTOM_DIR] # A directory to use for custom facts. d, [--debug], [--no-debug] # Enable debug output. [--external-dir=EXTERNAL_DIR]# A directory to use for external facts. [--hocon], [--no-hocon] # Output in Hocon format. j, [--json], [--no-json] # Output in JSON format. [--list-block-groups], [--no-list-block-groups] # List the names of all blockable fact groups. [--list-cache-groups], [--no-list-cache-groups] # List the names of all cacheable fact groups. l, [--log-level=LOG_LEVEL] # Set logging level. Supported levels are: none, trace, debug, info, warn, error, and fatal. [--block], [--no-block] # Disable fact blocking. [--cache], [--no-cache] # Disable loading and refreshing facts from the cache [--custom-facts], [--no-custom-facts]# Disable custom facts. [--external-facts], [--no-external-facts]# Disable external facts. [--ruby], [--no-ruby] # Disable loading Ruby, facts requiring Ruby, and custom facts. [--trace], [--no-trace] # Enable backtraces for custom facts. [--verbose], [--no-verbose] # Enable verbose (info) output. [--show-legacy], [--no-show-legacy] # Show legacy facts when querying all facts. y, [--yaml], [--no-yaml] # Output in YAML format. [--strict], [--no-strict] # Enable more aggressive error reporting. p, [--puppet], [--no-puppet] # Load the Puppet libraries, thus allowing Facter to load Puppet-specific facts.{noformat}
Jira (FACT-2513) command line help does flags incorrectly
Title: Message Title
Jesse Reynolds updated an issue
Facter / FACT-2513
command line help does flags incorrectly
Change By:
Jesse Reynolds
Running ` {{ facter -h ` }} to get online help does shows single letter command line options (flags) without the preceding dash ` {{ - ` }} . Eg ` {{ f ` }} instead of ` {{ -f ` }} {noformat}~ $ facter -hCommands: facter --list-block-groups # List block groups facter [options] [query] [query] [...] # facter help [COMMAND] # Describe available commands or one specific commandOptions: [--color], [--no-color] # Enable color output. c, [--config=CONFIG] # The location of the config file. [--custom-dir=CUSTOM_DIR] # A directory to use for custom facts. d, [--debug], [--no-debug] # Enable debug output. [--external-dir=EXTERNAL_DIR]# A directory to use for external facts. [--hocon], [--no-hocon] # Output in Hocon format. j, [--json], [--no-json] # Output in JSON format. [--list-block-groups], [--no-list-block-groups] # List the names of all blockable fact groups. [--list-cache-groups], [--no-list-cache-groups] # List the names of all cacheable fact groups. l, [--log-level=LOG_LEVEL] # Set logging level. Supported levels are: none, trace, debug, info, warn, error, and fatal. [--block], [--no-block] # Disable fact blocking. [--cache], [--no-cache] # Disable loading and refreshing facts from the cache [--custom-facts], [--no-custom-facts]# Disable custom facts. [--external-facts], [--no-external-facts]# Disable external facts. [--ruby], [--no-ruby] # Disable loading Ruby, facts requiring Ruby, and custom facts. [--trace], [--no-trace] # Enable backtraces for custom facts. [--verbose], [--no-verbose] # Enable verbose (info) output. [--show-legacy], [--no-show-legacy] # Show legacy facts when querying all facts. y, [--yaml], [--no-yaml] # Output in YAML format. [--strict], [--no-strict] # Enable more aggressive error reporting. p, [--puppet], [--no-puppet] # Load the Puppet libraries, thus allowing Facter to load Puppet-specific facts.{noformat}
Jira (FACT-2513) command line help does flags incorrectly
Title: Message Title Jesse Reynolds created an issue Facter / FACT-2513 command line help does flags incorrectly Issue Type: Bug Affects Versions: FACT 4.0.13 Assignee: Unassigned Components: CLI Created: 2020/03/30 10:55 PM Priority: Normal Reporter: Jesse Reynolds Running `facter h` to get online help does single letter command line options (flags) without the preceding dash ``. Eg `f` instead of `-f` ~ $ facter -h Commands: facter --list-block-groups # List block groups facter [options] [query] [query] [...] # facter help [COMMAND] # Describe available
Jira (PUP-10403) Puppet agent --help is missing the --tasks flag
Title: Message Title Nick Maludy created an issue Puppet / PUP-10403 Puppet agent --help is missing the --tasks flag Issue Type: Bug Affects Versions: PUP 6.14.0 Assignee: Unassigned Components: UX Created: 2020/03/30 6:39 PM Priority: Normal Reporter: Nick Maludy Puppet Version: 6.14.0 Puppet Server Version: N/A OS Name/Version: CentOS 7.7 When running `puppet parser validate path/to/bolt/plan.pp` it failed until i passed in `–tasks`, which was not present in the `–help` output of `puppet --help` or `puppet parser --help` or `puppet parser validate --help`. Desired Behavior: The `–tasks` parameter is shown when we pass in `--help`. Actual Behavior: $ puppet parser --help USAGE: puppet parser Interact directly with the parser.OPTIONS: --render-as FORMAT - The rendering format to use.
Jira (PUP-10402) Support TLS 1.3
Title: Message Title Josh Cooper created an issue Puppet / PUP-10402 Support TLS 1.3 Issue Type: Epic Assignee: Unassigned Created: 2020/03/30 4:44 PM Priority: Normal Reporter: Josh Cooper Puppet agents and server do not support TLS 1.3 yet. This is an epic for that work. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10154) Detect connection errors when using TLS 1.3 and using post-handshake authentication
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10154 Detect connection errors when using TLS 1.3 and using post-handshake authentication Change By: Josh Cooper Epic Link: PUP- 8550 10402 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.337392.1575326015000.25207.1585611900067%40Atlassian.JIRA.
Jira (PUP-7737) Add HTTP report processor setting for including system truststore
Title: Message Title Josh Cooper commented on PUP-7737 Re: Add HTTP report processor setting for including system truststore Passed CI in 5c6227417c 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.198103.1498609351000.25201.1585611482959%40Atlassian.JIRA.
Jira (PUP-10316) Update http report processor to use http client
Title: Message Title Josh Cooper commented on PUP-10316 Re: Update http report processor to use http client Passed CI in 5c6227417c 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.347625.1582698076000.25200.1585611482915%40Atlassian.JIRA.
Jira (PUP-10324) Forward http client requests to puppetserver
Title: Message Title Josh Cooper commented on PUP-10324 Re: Forward http client requests to puppetserver Passed CI in 5c6227417c 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.348081.1583171843000.25199.1585611482873%40Atlassian.JIRA.
Jira (PUP-10354) Add HTTP client yardocs and mark as private
Title: Message Title Josh Cooper commented on PUP-10354 Re: Add HTTP client yardocs and mark as private Passed CI in 5c6227417c 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.348573.1583350439000.25140.1585611420092%40Atlassian.JIRA.
Jira (PUP-10401) Pip package provider outputs warning on puppet run
Title: Message Title Josh Cooper commented on PUP-10401 Re: Pip package provider outputs warning on puppet run I think the problem is the pip3 provider requires the parent class pip directly. Later the autoloader tries to load the pip provider which triggers the warning. Note the autoloader doesn't check to see if a file has already been loaded outside of the autoloader. Deleting this line seems to fix things: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/pip3.rb#L4 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.352740.1585608902000.25050.1585610884414%40Atlassian.JIRA.
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Josh Cooper commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection I submitted a PR to improve our test for ruby's EOFError behavior, since ruby can automatically retry idempotent requests, which may mask the EOF problem (see PUP-3905) That said, this ticket was filed against puppet 3.7 and ruby 1.8.7, and as we've seen, ruby's behavior has changed over the years. Puppet 5.5.x ships with ruby 2.3.8 and puppet 6 requires ruby 2.3 or above, and both of those ruby versions contain the ruby fix to reconnect after EOF. So it appears this ticket has been overtaken by recent events, and I think we should close this ticket. If there are cases where a more recent ruby/puppet incorrectly handles this case (when the remote side closes the connection) please reopen this 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.51011.1410505537000.24810.1585609980128%40Atlassian.JIRA.
Jira (PUP-10401) Pip package provider outputs warning on puppet run
Title: Message Title Nick Burgan created an issue Puppet / PUP-10401 Pip package provider outputs warning on puppet run Issue Type: Bug Assignee: Unassigned Created: 2020/03/30 3:55 PM Priority: Normal Reporter: Nick Burgan Puppet Version: 6.14.0.135.gaf1499b7 (but may have started happening in earlier builds) Puppet Server Version: N/A, but using latest PE master build (rc2-37) OS Name/Version: centos 6, sles 12, ubuntu 18.04 When doing a puppet agent -t run, the following warnings are printed. /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: already initialized constant PIP_VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:18: warning: previous definition of PIP_VERSION was here /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: already initialized constant PIP_VERSION_RANGE /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:19: warning: previous definition of PIP_VERSION_RANGE was here
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.282135.1540387252000.23860.1585591560088%40Atlassian.JIRA.
Jira (PDB-4172) Allow metrics during startup
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4172 Allow metrics during startup Change By: Nick Burgan Story Points: 5 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.282135.1540387252000.23859.1585591560044%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Nick Burgan Sprint: HA Team (Ready For Work) 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.280669.1539661927000.23856.1585591440084%40Atlassian.JIRA.
Jira (PDB-4157) Review impact of connection limits in clj-http-client
Title: Message Title Nick Burgan updated an issue PuppetDB / PDB-4157 Review impact of connection limits in clj-http-client Change By: Nick Burgan Story Points: 5 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.280669.1539661927000.23855.1585591440039%40Atlassian.JIRA.
Jira (PUP-10400) apply splay after network issues resolved
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10400 apply splay after network issues resolved Change By: Josh Cooper Component/s: puppet-runtime Key: PA PUP - 3174 10400 Project: Puppet Agent 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.351563.1585575424000.23810.1585590420041%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Nick Maludy commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update I'm using both RHEL 7.7 and CentOS 7.7, yes. 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.348520.1583329295000.23657.1585588080276%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Josh Cooper commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update Ah I tested using ubuntu xenial but I see the report is for CentOS 7.7.1908. Nick Maludy are you using that centos too? 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.348520.1583329295000.23633.1585587720076%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Nick Maludy commented on PUP-10351 Re: Puppet Agent fails to self-restart on config change or update FYI manually restarting the Puppet service seems to fix the problem. 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.348520.1583329295000.23585.1585586520091%40Atlassian.JIRA.
Jira (FACT-2512) Facter doesn't run on Raspbian
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2512 Facter doesn't run on Raspbian Change By: Bogdan Irimie 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.351552.1585568068000.23480.1585580220029%40Atlassian.JIRA.
Jira (FACT-2512) Facter doesn't run on Raspbian
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2512 Facter doesn't run on Raspbian Change By: Bogdan Irimie Assignee: 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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.351552.1585568068000.23479.1585580160032%40Atlassian.JIRA.
Jira (FACT-2512) Facter doesn't run on Raspbian
Title: Message Title Bogdan Irimie commented on FACT-2512 Re: Facter doesn't run on Raspbian Thank you for reporting the issue Matt Love. Plase make a PR on https://github.com/puppetlabs/facter-ng/pulls At this point in time we have to manually add new distributions and OSes in general, but we are evaluating a new mechanism that will be able to automatically detect OSes. Until this new mechanism is ready please make a PR and add Raspbian similar to how we have added ElementaryOS https://github.com/puppetlabs/facter-ng/pull/408/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.351552.1585568068000.23475.1585579620024%40Atlassian.JIRA.
Jira (PUP-10399) Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number
Title: Message Title
Lucas Young updated an issue
Puppet / PUP-10399
Error: wrong number of arguments (given 2, expected 1) Deferred function doesn't return file / line number
Change By:
Lucas Young
*Puppet Version: Puppet 6.10.2* *Puppet Server Version: 2019.2.2* *OS Name/Version: Ubuntu 16.04**+Actual Behavior:+* When setting up a deferred function if a difference different number of arguments are passed into the dispatch declaration versus the actual method a Puppet run will generate the following error: "*Error: Failed to apply catalog: wrong number of arguments (given 2, expected 1)*"The issue is that none of the file / line number information is returned as part of the error message above, offering no trace back to the origination of the error in the code base. +*Code example:*+{code:java}dispatch :example do param 'String', :stuff optional_param 'String', :morestuffenddef example(stuff) return stuff + 1end {code}When the same code is ran and it is not a Deferred function, a file / line number is included in that error message. *+Desired behavior:+* Generate an error message with a line / file indication: "Error: Failed tp apply catalog, wrong number of arguments (given 2, expected 1) (file: /home/test_user/Working/custom_function_repro/modules/test_module/manifests/init.pp, line: 2, column: 8)"
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10300) find_file function returns path even if absolute path does not exist
Title: Message Title
Florian Faltermeier commented on PUP-10300
Re: find_file function returns path even if absolute path does not exist
Hello Josh, I'm still getting a courious behaviour: As an example: $file_exists = find_file('/etc/testfile') # file does not exist on disk within this directory unless $file_exists { # Puppet code, do something } the unless statement wouldn't be executed. Or I am doing something wrong? Florian
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.346683.1582114324000.23437.1585571760033%40Atlassian.JIRA.
Jira (FACT-2512) Facter doesn't run on Raspbian
Title: Message Title Matt Love updated an issue Facter / FACT-2512 Facter doesn't run on Raspbian Change By: Matt Love Summary: Facter fails to handle doesn't run on Raspbian distribution 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.351552.1585568068000.23435.1585568160029%40Atlassian.JIRA.
Jira (FACT-2512) Facter fails to handle Raspbian distribution
Title: Message Title Matt Love created an issue Facter / FACT-2512 Facter fails to handle Raspbian distribution Issue Type: Bug Affects Versions: FACT 4.0.13 Assignee: Unassigned Components: Facter 4 Created: 2020/03/30 4:34 AM Priority: Normal Reporter: Matt Love When I run facter on a RaspberryPi device running Raspbian I get the following error messages. [2020-03-30 07:49:00.202966 ] ERROR Facter::ClassDiscoverer - There is no module named Raspbian Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/provider/group/groupadd: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/type/group: Could not autoload puppet/provider/group/groupadd: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not run: Could not autoload puppet/type/group: Could not autoload puppet/provider/group/groupadd: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass pi@RevPi33171:~ $ I have a basic PR that I'm testing that adds Raspbian, similar to FACT-2492
Jira (FACT-2498) Internal fact loader should not load all fact from hierarchy
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2498 Internal fact loader should not load all fact from hierarchy Change By: Bogdan Irimie Assignee: 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 https://groups.google.com/d/msgid/puppet-bugs/JIRA.351168.1585213496000.23396.158980026%40Atlassian.JIRA.
Jira (FACT-2510) Start office hours
Title: Message Title Bogdan Irimie commented on FACT-2510 Re: Start office hours Talked with Ben Ford and planned office hours once a month, starting with 7th of April. 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.351404.1585316348000.23395.158920029%40Atlassian.JIRA.
Jira (PUP-10351) Puppet Agent fails to self-restart on config change or update
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10351 Puppet Agent fails to self-restart on config change or update Change By: Luchian Nemes Assignee: Luchian Nemes 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.348520.1583329295000.23390.1585554840043%40Atlassian.JIRA.
Jira (PUP-10371) Add metric for Puppet Agent run
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10371 Add metric for Puppet Agent run Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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.23375.1585550520117%40Atlassian.JIRA.
