Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1431438

Summary: RNG: Incorrect mouseover description of /dev/urandom
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.1.3CC: bugs, michal.skrivanek, nsimsolo
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-13 10:37:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Nisim Simsolo 2017-03-12 14:58:34 UTC 
Description of problem:
When standing with the mouse over "/dev/urandom source" the next description appers: "Random Number Generator source 'urandom' is not supported by the cluster" although this source is supported and enabled by default on new VMs and attached to VM properly.

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. Browse webadmin -> virtual machines tab -> new VM -> random generator tab
2. Mouseover /dev/urandom (not on the tool tip question mark)
3.

Actual results:
The next description appears: "Random Number Generator source 'urandom' is not supported by the cluster" although /dev/urandom is enabled by default and cluster/DC compatibility version is 4.1.

Expected results:
/dev/urandom source radio button should not be grayed out and the mouseover description should be fixed.

Additional info:
Screenshot attached
Comment 1 Nisim Simsolo 2017-03-12 14:59:53 UTC 
Created attachment 1262230 [details]
screenshot
Comment 2 Michal Skrivanek 2017-03-13 10:37:17 UTC 

*** This bug has been marked as a duplicate of bug 1431435 ***