Issue #8358 has been updated by Jeff Weiss. Target version deleted (1.6.x)
---------------------------------------- Bug #8358: ec2 fact runs incorrectly on some xen setups https://projects.puppetlabs.com/issues/8358#change-63730 Author: R.I. Pienaar Status: Accepted Priority: Normal Assignee: Category: library Target version: Keywords: ec2 Branch: Affected Facter version: 1.6.0 When a xen dom0 is setup in bridging mode the xen scripts will create a bridge and a bunch of virtual interfaces all with the MAC address FE:FF:FF:FF:FF:FF, this results in domU with the arp fact set to this which triggers the ec2 facts incorrectly. <pre> % facter arp fe:ff:ff:ff:ff:ff </pre> >From the ec2.rb: <pre> def can_connect?(wait_sec=2) url = "http://169.254.169.254:80/"; Timeout::timeout(wait_sec) {open(url)} return true rescue Timeout::Error return false rescue return false end def has_ec2_arp? !!(Facter.value(:arp) == "fe:ff:ff:ff:ff:ff") end if (has_euca_mac? || has_ec2_arp?) && can_connect? . . . </pre> So since on this specific setup the has_ec2_arp? method returns true the can_connect? method gets run which has a 2 second timeout and it will fail to connect. This fact runs twice resulting in a 4 second slow down. This is on CentOS 5.6 -- 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.
