Jira (MCO-3) CLONE - A single malformed fact can break mcollective fact filtering in PE

[John Duarte (JIRA)]

Title: Message Title

John Duarte commented on an issue   Re: CLONE - A single malformed fact can break mcollective fact filtering in PE Pieter Loubser yes the spec tests in this PR are sufficient for testing the expectations of the YAML_facts. cc: Kenn Hussey Add Comment   MCollective / MCO-3 CLONE - A single malformed fact can break mcollective fact filtering in PE We have a cron job that dumps facter output as a yaml file to /etc/puppetlabs/mcollective/facts.yaml. If this file gets corrupted, or bad yaml is written, or debug output ends up in it, fact filtering no longer works. If a fact is bad or not returning the right parseable output, then not being able to filter by it could be expected. But a single bad / m... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.