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

Bug 1356172

Summary:	the message "snapshot created in different cluster version" is shown all the time
Product:	[oVirt] ovirt-engine	Reporter:	Tomas Jelinek <tjelinek>
Component:	BLL.Virt	Assignee:	Marek Libra <mlibra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	sefi litmanovich <slitmano>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.0.0	CC:	bugs, mgoldboi, michal.skrivanek
Target Milestone:	ovirt-4.0.4	Keywords:	UserExperience
Target Release:	4.0.4	Flags:	rule-engine: ovirt-4.0.z+ rule-engine: planning_ack+ michal.skrivanek: devel_ack+ mavital: testing_ack+
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:	2016-09-26 12:39:05 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:

Description Tomas Jelinek 2016-07-13 14:51:16 UTC

Reproduce:
- have a running VM
- create a snapshot with memory
- turn off the VM
- press preview

result: the "The selected snapshot's memory can't be properly restored since it was created in different cluster version. Please confirm the memory shall be restored anyway." is shown even the VM is still in the same cluster.

If you check the "restore anyway" checkbox the memory is restored and seems to be working properly.

Additional info:
The reason seems to be that the check in SnapshotModel.isVMWithMemoryCompatible() relies on the vm.getClusterCompatibilityVersionOrigin(); while SnapshotManager.updateVmFromConfiguration() replaces it by vm.setClusterCompatibilityVersionOrigin(oldVmStatic.getClusterCompatibilityVersionOrigin());

Comment 2 sefi litmanovich 2016-09-13 14:55:02 UTC

Verified with rhevm-4.0.4.2-0.1.el7ev.noarch.

The message did not appear when running the flow in the description.
The message did not appear when the vm was set with custom ccv 3.6 before taking the snapshot and set to custom ccv 4.0 after snapshot is taken and before previewing - this makes sense as in this case ccv is managed manually by the user.
The message did appear when snapshot was created on a 3.6 cluster and was previewed after the cluster's upgrade to 4.0 ccv.