refresh-mcollective-metadata creates superfluous emails for spurious facter errors

[terrorobe]

Some facter modules can cause temporary errors with output like

From: root@bka-001-10.bka.cloud.example.com (Cron Daemon)
To: root@bka-001-10.bka.cloud.example.com
Subject: Cron <root@bka-001-10> /usr/share/mcollective/plugins/refresh-mcollective-metadata
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <PATH=/opt/puppet/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/lib64/fluent/ruby/bin:/usr/lib/fluent/ruby/bin>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <E1YmisL-000Bxj-QO@bka-001-10.bka.cloud.example.com>
Date: Mon, 27 Apr 2015 15:15:05 +0200

Device "veth767d43e4-9" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth767d43e4-9" does not exist.
Device "veth78e0975b-8" does not exist.
Device "veth78e0975b-8" does not exist.

shown for a single run.

This has been discussed in the past (e.g. https://projects.puppetlabs.com/issues/15035) but apparently seems to be unfixed in recent facter versions (in our case: 2.4.1-1puppetlabs1)

It would be great if the cronjob would be silenced by default (> /dev/null 2>&1)

[igalic]

@antafalos: ping

[terrorobe]

Done and done!