Issue #14366 has been updated by Jeremy Brake. Assignee changed from Ramin K to Jeff McCune
Hi Jeff, I'm seeing the same issue under Centos6 with 2.6 kernel (still broken in 6.17), but am not in a position to run the latest version of Puppet, and therefore facter. Is there a way to work around this (ideally in Puppet-2.6.7) by strategically overriding with custom facts, applied to known AWS instances and/or by exporting all of the ec2 and vpc facts to an external facts config and removing the dependancies? ---------------------------------------- Bug #14366: virtual => physical and is_virtual => false on EC2 https://projects.puppetlabs.com/issues/14366#change-81828 Author: Kevin O'Connor Status: Needs More Information Priority: Normal Assignee: Jeff McCune Category: cloud - ec2 Target version: Keywords: Branch: Affected Facter version: 1.6.8 As described: [root@production-web-d95fb6bf ~]# facter | grep -i virtual ec2_profile => default-paravirtual is_virtual => false virtual => physical [root@production-web-d95fb6bf ~]# facter --version 1.6.8 [root@production-web-d95fb6bf ~]# cat /etc/*-release Amazon Linux AMI release 2012.03 is_virtual should be true, right? -- 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.
