Issue #15391 has been updated by C Lang.
arp -a in a vpc does not contain this - looks like a normal arp table. The only special value I seem to see consistently is an entry for 169.254.169.250 with a varying MAC. I'm not sure I'd rely on that without confirmation from Amazon. It may be a Windows activation service IP used in VPCs. I will open a ticket with Amazon and see if I can get an answer. ---------------------------------------- Bug #15391: Facter Windows fails to detect EC2 when running in VPC https://projects.puppetlabs.com/issues/15391#change-67185 Author: C Lang Status: Investigating Priority: High Assignee: Category: library Target version: Keywords: ec2,arp,vpc,windows Branch: Affected Facter version: 1.6.10 Apparently facter relies on seeing the gateway address in arp with FF:FF:FF:FF:FF:FF as the MAC. Unfortunately, this isn't present inside of a VPC, so Facter fails completely. Is it possible to skip the arp check and query the meta data? -- 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.
