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

Bug 1177234

Summary: Instance type: cluster with compatibility version 3.4 should reject re-run of VM with RNG enabled.
Product: [Retired] oVirt Reporter: Nisim Simsolo <nsimsolo>
Component: ovirt-engine-coreAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3CC: bugs, ecohen, gklein, lsurette, michal.skrivanek, ofrenkel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Reopened
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: ovirt-3.5.1_rc1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 12:27:45 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:
Bug Depends On:    
Bug Blocks: 1193058, 1196662, 1197441    
Attachments:
Description Flags
rejection-message
none
vdsm log
none
engine log
none
powering off running VM after enabling RNG on instance type none

Description Nisim Simsolo 2014-12-25 09:38:45 UTC 
Description of problem:
Powering off > running VM (of 3.4 cluster) related on instance type that changed to rng enabled, should be rejected by RHEVM UI with an appropriate error message. 

Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.27.el6ev.noarch
vdsm-4.16.8.1-4.el6ev.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
sanlock-2.8-1.el6.x86_64
libvirt-0.10.2-46.el6_6.2.x86_64

How reproducible:
Consistantly

Steps to Reproduce:
1. Create new data center with compatibility version 3.4.
2. Create new cluster with compatibility version 3.4.
3. Add new host to this cluster.
4. Create new instance type with "random generator" disabled.
5. Create new VM related on this instance type.
6. run VM and install OS on it.
7. Change instance type "random generator" to enable.
8. Power off and run VM again.

Actual results:
VM loads without rejecing the new configuration (although rng is disabled in edit VM > random generator tab).

Expected results:
RHEVM should reject the run of VM with an appropriate message.

Additional info:
While creating new VM with rng enabled on instance type, the RHEVM rejecting the running of VM (see attached rejection_message.png)

logs attached.
Comment 1 Nisim Simsolo 2014-12-25 09:39:39 UTC 
Created attachment 972951 [details]
rejection-message
Comment 2 Nisim Simsolo 2014-12-25 09:40:43 UTC 
Created attachment 972952 [details]
vdsm log
Comment 3 Nisim Simsolo 2014-12-25 09:42:47 UTC 
Created attachment 972953 [details]
engine log
Comment 4 Nisim Simsolo 2014-12-25 09:45:05 UTC 
Created attachment 972964 [details]
powering off running VM after enabling RNG on instance type
Comment 5 Tomas Jelinek 2015-01-12 13:03:42 UTC 
well, the behavior should be like this:
You should be able to use the instance type which sets the RNG device, but if you use it on a cluster which does not support it, it should not be taken from the instance type. So, the bug here is the last part (mentioned in "Additional info") - the new VM should have been created and started successfully in that case and the attached bug is fixing this.

But I see it is not explained on the wiki. So, added: http://www.ovirt.org/Features/Instance_Types#Cluster_Compatibility
Comment 6 Sandro Bonazzola 2015-01-15 14:15:30 UTC 
This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
Comment 7 Sandro Bonazzola 2015-01-21 16:03:42 UTC 
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.
Comment 8 Eyal Edri 2015-02-26 12:33:07 UTC 
this ovirt bug was fixed during 3.5.1 cycle and is included in the build, and therefore should be verified.
Comment 9 Nisim Simsolo 2015-03-01 15:34:41 UTC 
Verified: Verified: rhevm-3.5.1-0.1.el6ev.noarch
sanlock-3.2.2-2.el7.x86_64
vdsm-4.16.12-2.el7ev.x86_64
qemu-kvm-rhev-2.2.0-5.el7.x86_64

Also, Test case edited according to new details added in wiki - cluster compatibility section.