Issue #7559 has been updated by Jeff McCune.

On Sunday, February 3, 2013, wrote:

>   Issue #7559 has been updated by Jonathan Sabo.
>
>
> 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
>

Are you sure you're running the latest code in the branch I published?
 This looks like you're still running 1.6.17, which isn't the latest.

This will definitely be fixed with RHEL as well as other
supported platforms.

Please let me know if you'd like instructions on how to run Facter from the
topic branch that contains this fix.


> [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 <http://169.254.169.254/latest/meta-data/ami-idami-cc5af9a5>
> ------------------------------
> Feature #7559: Fact for identifying Amazon VPC 
> instances.<https://projects.puppetlabs.com/issues/7559#change-82378>
>
>    - Author: Nigel Kersten
>    - Status: Merged - Pending Release
>    - Priority: Normal
>    - Assignee:
>    - Category: cloud - ec2
>    - Target version: 2.0.0
>    - Keywords: vpc ec2 arp
>    - 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.
>
> /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
>
> 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:
>
> def has_euca_mac?
>  !!(Facter.value(:macaddress) =~ %r{^02:67:4[eE]:})
> end
>
> ------------------------------
>
> 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
>
----------------------------------------
Feature #7559: Fact for identifying Amazon VPC instances.
https://projects.puppetlabs.com/issues/7559#change-82389

Author: Nigel Kersten
Status: Merged - Pending Release
Priority: Normal
Assignee: 
Category: cloud - ec2
Target version: 2.0.0
Keywords: vpc ec2 arp
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to