Issue #14366 has been updated by Ramin K.
Jeff,
Thanks much for the pointer to hub, that helped. Nice thing for a blog post if
you so inclined as well.
[email protected] ~/src/facter $ bundle exec facter | egrep
"virt|facter|operating|instance"
ec2_instance_id => i-1111111
ec2_instance_type => c1.xlarge
ec2_profile => default-paravirtual
facterversion => 2.0.0-rc4
is_virtual => true
kernelrelease => 3.2.0-36-virtual
operatingsystem => Ubuntu
operatingsystemrelease => 12.04
virtual => xenu
That looks much better. I think the problem was introduced in the 3.x Linux
kernel which changed the files in /proc/xen/ I believe this commit was the fix.
https://github.com/puppetlabs/facter/commit/976b7af24d641e589121d30e37bacc983d79cc0a
Let me know if you need any more info.
----------------------------------------
Bug #14366: virtual => physical and is_virtual => false on EC2
https://projects.puppetlabs.com/issues/14366#change-81688
Author: Kevin O'Connor
Status: Needs More Information
Priority: Normal
Assignee: Ramin K
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.
