Issue #19018 has been updated by Hailee Kenney. Status changed from Unreviewed to Needs More Information Assignee set to Maxime Caumartin
Since this is happening with Facter 1.6.17, would it be possible for you to see if you can recreate this error again in the newest Facter version (1.7)? A lot of changes and fixes went into this version, and it’d be great if we could first make sure that this issue hasn’t already been resolved. I’ve put this ticket’s status into “Needs more Information” and assigned it to you. Please either (a) update it with the information I’ve requested and re-assign it to me if you need more help, or (b) change the status to “Closed” if you were able to resolve the issue on your own. Thanks! ---------------------------------------- Bug #19018: Wrong virtualisation type detected when running an openVZ ve in a KVM host https://projects.puppetlabs.com/issues/19018#change-90820 * Author: Maxime Caumartin * Status: Needs More Information * Priority: Normal * Assignee: Maxime Caumartin * Category: * Target version: * Keywords: virtual,kvm,openvz * Branch: * Affected Facter version: 1.6.17 ---------------------------------------- When facter is run from a openVZ container, and that the host is itself a KVM vm, the result of the 'virtual' fact will be KVM. Since there is two levels of virtualisation, this fact should give the inner-most virtualisation type instead, 'openvzve'. -- 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.
