Description of problem: When creating VM pool from template with RNG /dev/urandom enabled, in the webadmin it looks like the feature is disabled (edit VM -> random generator -> "Random Generator enabled" checkbox is unchecked) but observing qemu-kvm process and vdsm.log shows that /dev/urandom source is available on the VM. Version-Release number of selected component (if applicable): ovirt-engine-4.1.1.3-0.1.el7 qemu-kvm-rhev-2.6.0-28.el7_3.6.x86_64 vdsm-4.19.7-1.el7ev.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 sanlock-3.4.0-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create VM with RNG -> /dev/urandom source enabled. 2. Create template from this VM and create pool of 5 VMs from this template. 3. Browse webadmin -> edit VM -> random generator tab Actual results: "Random Generator enabled" checkbox is unchecked. Observing qemu-kvm process and vdsm.log shows that /dev/urandom source is available on the VM. It is possible to generate random number from the VM using /dev/urandom source. Expected results: If RNG is enabled on the VM than "Random Generator enabled" checkbox should be checked. Additional info: vdsm.log and engine.log attached (pool VMs name: 11pool11).
Created attachment 1260789 [details] vdsm.log
Created attachment 1260790 [details] engine.log
I guess that if you now add new VMs to the pool the new VMs will have this random source actually disabled which makes this bug a bit more important.
Just tested it, same behavior obvserved when increasing number of VMs in pool (RNG disabled in webadmin although it's not actually disabled)
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.1.3.1' doesn't contain patch 'https://gerrit.ovirt.org/77471'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.1.3.1 For more info please contact: infra
Verified: libvirt-client-3.2.0-9.el7.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.10.x86_64 sanlock-3.5.0-1.el7.x86_64 vdsm-4.19.18-1.el7ev.x86_64