Issue #20274 has been updated by Charlie Sharpsteen. Status changed from Unreviewed to Needs More Information Assignee changed from Charlie Sharpsteen to Celia Cottle
Did we ever get a re-production case out of this one? Facter on the CentOS VM I tested was behaving sanely when eth0 was renamed to eth2. Also, can't find any stock Facter code in PE 2.8.1 that calls arping. ---------------------------------------- Bug #20274: No eth0 causes error https://projects.puppetlabs.com/issues/20274#change-90763 * Author: Celia Cottle * Status: Needs More Information * Priority: Normal * Assignee: Celia Cottle * Category: * Target version: * Keywords: customer * Branch: * Affected Facter version: ---------------------------------------- When the mcollective-metadata cron runs, the lack of eth0 causes this error to appear "arping: unknown iface eth0", which ends up spamming logs every run. The customer also got the error when manually running facter: # facter -p | grep eth arping: unknown iface eth0 interfaces => eth3,lo ipaddress_eth3 => xx.xx.xx.xx macaddress_eth3 => 00:15:5D:AB:xx:xx netmask_eth3 => 255.255.252.0 network_eth3 => xx.xx.xx.0 Currently they are working around it with "# Puppet Name: pe-mcollective-metadata 0,15,30,45 * * * * /opt/puppet/sbin/refresh-mcollective-metadata > /dev/null 2>&1" I'm looking into a workaround that's a little cleaner and only target the eth0 fact. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
