Issue #11196 has been updated by Ken Barber.
Hmm. Your going to hate me but - I wonder how many people are using 'arp' as a way of detecting there machine is an EC2 host. We might need to socialise such a change with the community first. So I have two thoughts: * Lets perhaps revert your code to what it was - leave arp around * Raise a separate ticket to deprecate arp (or fix it properly perhaps?) - a ticket to discuss the future of 'arp' at least. Its probably the best conservative approach to keep backwards compatibility. This way - it can probably go into 1.6.x as well. What do you think? ---------------------------------------- Bug #11196: EC2 facts do not get created when the arp table contains more than 1 entry (patch included) https://projects.puppetlabs.com/issues/11196 Author: Pieter Lexis Status: Investigating Priority: Normal Assignee: Category: library Target version: Keywords: ec2 arp Branch: Affected Facter version: 1.6.3 We have an EC2 instance with a QEMU vm on it (don't ask, we cried as well when this was the only solution). This means that we have a bridge interface on the EC2 instance and that the arp table contains more than 1 entry (on EC2 the only entry is the gateway). The code in the arp module does not take this into account. Than the ec2 code infers that this isn't an ec2 instance (and doesn't create the ec2 facts), but it is. If you would be running a VPN service on EC2, this bug could hit you as well (as you have more than 1 interface). This patch fixes that. Pull request follows. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
