Issue #7559 has been updated by Rafael Correa. Support Urls deleted (https://support.puppetlabs.com/tickets/840)
I had the same issue Jonathan. The problem happens when facter defaults the value of the "virtual" fact to the output of virt-what. It says "xen" instead of "xenu", which breaks the logic implemented in https://github.com/puppetlabs/facter/commit/ce18220fcb93e13ff459d2b4abcf18a96c658b87 My workaround solution to make it work on VPC instances was: 1-) Uninstall the RPM version of facter. You'll need the latest version from github (at the time I was writing this comment, this was the last commit: https://github.com/puppetlabs/facter/commit/ac28a515ac405523c456630fd6389df5d13a702f), which is not packaged yet (not even as a gem). 2-) Uninstall virt-what package from your EC2 VPC instance, and let the others implementation of the "virtual" fact take care of the job for you. It returned "xenu" as expected by the logic of the commit that solves this issue, and now I can use the ec2 facts on my puppet scripts. I've tested it on CentOS 6.4. Regards, hope it helps. Jonathan Sabo wrote: > I've been trying to get the ec2 facts to work in VPC on Redhat's AMI: > RHEL-6.3-Starter-x86_64-1-Hourly2 (ami-cc5af9a5) and even with the latest > code it's not working and I think it's because facter virtual reports xen and > not xenu. Is this going to work for RHEL AMI's? > > Check it out. > > [root@ip-10-146-2-71 ~]# rpm -qa | grep facter > facter-1.6.17-1.el6.x86_64 > > [root@ip-10-146-2-71 ~]# cat /etc/redhat-release > Red Hat Enterprise Linux Server release 6.3 (Santiago) > > [root@ip-10-146-2-71 ~]# facter virtual > xen > > [root@ip-10-146-2-71 ~]# curl -s > http://169.254.169.254/latest/meta-data/ami-id > ami-cc5af9a5 ---------------------------------------- Feature #7559: Fact for identifying Amazon VPC instances. https://projects.puppetlabs.com/issues/7559#change-94023 * Author: Nigel Kersten * Status: Merged - Pending Release * Priority: Normal * Assignee: * Category: cloud - ec2 * Target version: 2.0.0 * Keywords: vpc ec2 arp customer * Branch: https://github.com/puppetlabs/facter/pull/387 * Affected Facter version: 1.6.10 ---------------------------------------- (From the list) I ran into a buglet in facter 1.5.9rc6 (from tmz repo). In normal AWS instances it works great. In VPC instances if doesn't work. This seems to be because VPC instances don't use the fe:ff:ff:... MAC addresses. <pre> /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 02:67:4E:E1:26:30 inet addr:172.17.129.24 ... /sbin/arp Address HWtype HWaddress Flags Mask Iface 169.254.169.253 ether 02:67:4E:C0:00:01 C eth0 172.17.128.1 ether 02:67:4E:C0:00:01 C eth0 /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 02:67:4E:DA:58:16 inet addr:172.17.128.126 /sbin/arp Address HWtype HWaddress Flags Mask Iface 169.254.169.253 ether 02:67:4E:C0:00:01 C eth0 172.17.128.1 ether 02:67:4E:C0:00:01 C eth0 </pre> Of the two VPC EC2 instances I've seen, the MAC address always start with 02:67:4E. I have only seen two instances, both in the same VPC, so I don't know if this holds for every VPC instance, YMMV. in ec2.rb , the following seemed to work: <pre> def has_euca_mac? !!(Facter.value(:macaddress) =~ %r{^02:67:4[eE]:}) end </pre> -- 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. For more options, visit https://groups.google.com/groups/opt_out.
