OK. First of all, i am pasting here the commit that fixed that bug on puppet repositories :
https://github.com/puppetlabs/facter/commit/5c653e98e97ba8e83a46b8e0c1fd72dfe672964b You can see that this fix is really close to the patch I provided you. Here are the SRU explanation I can provide you. [Impact] When running Ubuntu OS with Proxmox VE updated on version 2.3, the output for the /proc/cpuinfo file changes on the running VM, and the facter utils will not recognized the VM as being 'virtual', but as being 'physical' [Test Case] [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance ** Attachment added: "test case with bug" https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1170325/+attachment/3652273/+files/new_version.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1170325 Title: Facter 1.6.X not considering Qemu/KVM virtual type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1170325/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
