Issue #7559 has been updated by Jeff McCune.

Assignee set to Martijn Heemels

This doesn't seem to be an issue in recent releases of Facter.  I posted 
similar information in #14366 but I'll cross-post it here to get as much 
feedback as possible.

Martijn, if you could easily configure your instances to install up to date 
packages from our own repository, would this be an acceptable solution to this 
issue?

It looks like this issue is fixed in recent versions of Facter.  I think Amazon 
simply needs to update the version of Facter they make available to the AMI.  I 
checked facter running on amzn-ami-pv-2012.09.0.x86_64-ebs (ami-1624987f) in 
both a VPC and "normally" and here's what I get:

<pre>
[ec2-user@ip-10-204-211-77] (master)(dirty)[██▁]~/src/facter 
$ bundle exec facter virtual
xenu
[ec2-user@ip-10-204-211-77] (master)(dirty)[██▁]~/src/facter 
$ bundle exec facter is_virtual
true
[ec2-user@ip-10-204-211-77] (master)(dirty)[██▁]~/src/facter 
$ git describe
1.6.17-467-g05f2519
</pre>

I think the main question at this point in time is; how can we make it as 
smooth and robust as possible to get recent Facter releases into these affected 
instances.  Would you run Facter from our repositories if it were easy and 
well-supported to do so?

-Jeff
----------------------------------------
Feature #7559: Fact for identifying Amazon VPC instances.
https://projects.puppetlabs.com/issues/7559#change-81682

Author: Nigel Kersten
Status: Accepted
Priority: Normal
Assignee: Martijn Heemels
Category: library
Target version: 
Keywords: vpc ec2 arp
Branch: 
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to