Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Konrad Scherer commented on PUP-9816 Re: puppet parser validate version 6.6.0 does not accept STDIN properly I see it both with empty files and large valid puppet files like my manifests/nodes.pp Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315541.1562618702000.16562.1563222900429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9816) puppet parser validate version 6.6.0 does not accept STDIN properly
Title: Message Title Konrad Scherer created an issue Puppet / PUP-9816 puppet parser validate version 6.6.0 does not accept STDIN properly Issue Type: Bug Affects Versions: PUP 6.6.0, PUP 6.5.0 Assignee: Unassigned Components: Compiler Created: 2019/07/08 1:45 PM Priority: Minor Reporter: Konrad Scherer Puppet Version: 6.6.0 and 6.5.0 Puppet Server Version: N/A OS Name/Version: Ubuntu 19.04 using bionic packages 6.6.0-1bionic Passing code over stdin to puppet parser fails with 'Error: undefined method `message' for nil:NilClass'. I was able to reproduce with 6.5.0 and 6.6.0, but not with 6.4.2 Desired Behavior: Validation of code using filename or stdin should be identical Actual Behavior: > touch foo.pp > puppet parser validate foo.pp > cat foo.pp | puppet parser validate Error: undefined method `message' for nil:NilClass Error: Try 'puppet help parser validate' for usage I noticed this because emacs flycheck uses stdin to do syntax checking. Note that the documentation (man puppet parser) states that this is a valid way to submit output: EXAMPLES Validate from STDIN: $ cat init.pp | puppet parser validate
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Konrad Scherer created an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Components: Puppet Server Created: 28/Oct/14 8:22 AM Priority: Normal Reporter: Konrad Scherer I use the nagios check_puppet.rb script to detect puppet run failures. https://github.com/ripienaar/monitoring-scripts/blob/master/puppet/check_puppet.rb I recently introduced a duplicate resource in my manifests for a few of my machines, but the script did not detect that the puppet run had failed. My other check for the age of the last_run_summary.yaml file did not trigger because puppet agent was updating this file. The last_run_summary looks like this: — resources: scheduled: 0 changed: 0 failed: 0 skipped: 0 total: 357 restarted: 0 out_of_sync: 0 failed_to_restart: 0 events: failure: 0 total: 0 success: 0 changes: total: 0 time: sysctl: 0.001234 service: 1.877718 anchor: 0.00448 ssh_authorized_key: 0.009279 group: 0.001692 config_retrieval: 0.870559930801392 last_run: 1414505487 filebucket: 0.00015 cron: 0.004659 schedule: 0.000962 file: 5.429886 host: 0.000658 exec: 2.216259 total: 11.4154379308014 package: 0.660641 user: 0.33
