Issue #11196 has been updated by Pieter Lexis.

If you don't mind me asking, what is the use of this fact at all?

    $ sudo arp -en -i eth0 | sed -e 1d
    172.29.96.252            ether   40:61:86:51:69:5f   C                     
eth0

    $ ping -c 1 172.29.96.31
    PING 172.29.96.31 (172.29.96.31) 56(84) bytes of data.
    64 bytes from 172.29.96.31: icmp_req=1 ttl=64 time=0.336 ms
    --- 172.29.96.31 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.336/0.336/0.336/0.000 ms

    $ sudo arp -en -i eth0 | sed -e 1d
    172.29.96.31             ether   bc:ae:c5:aa:52:1b   C                     
eth0
    172.29.96.252            ether   40:61:86:51:69:5f   C                     
eth0

The fact would change from 172.29.96.252 to 172.29.96.31.....

The arp module creates a fact 'arp' if and only if the first entry in the 
arptable is "fe:ff:ff:ff:ff:ff". Why is this anyway (the only module using this 
fact is ec2)?

I could check the arp table in the ec2 module and filter for fe:ff:ff:ff:ff:ff 
in that module... But it kind-of defeats the purpose of having access to facts 
internally in the first place(would fix this issue though).
----------------------------------------
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.

Reply via email to