Bug 1857116

Summary:	Warn against attaching storage domain to different cluster level
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	Documentation	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	Lukas Svaty <lsvaty>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.1	CC:	adahms, michal.skrivanek, royoung
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:	2020-07-19 17:28:53 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 Arik 2020-07-15 07:22:27 UTC

Users can detach a storage domain from one data center and attach it to a different cluster. Then by importing the "unregistered" entities, the templates and VMs from the former data center can be "registered" to the latter data center.

This mechanism was originally meant for disaster recovery - the storage device is being backed up and when the primary data center is disrupted, the storage device can be attached to a secondary data center where the templates and VMs can be registered to.

However, people found out that this mechanism can work for upgrades. By detaching a storage domain from data center X and attaching it to data center Y that is of a newer version, the templates and VMs can be move between those versions without needing to export and import the VMs and without the risk of disrupting the primary data center.

But now (oVirt 4.4) that templates and VMs need to be adjusted during upgrades, this wouldn't work without further changes. While we can treat this by adjusting the "registered" templates and VMs as if they were imported, this is conceptually wrong - entities should be registered to the same cluster version they were unregistered from.

Comment 1 Michal Skrivanek 2020-07-15 11:22:26 UTC

this should be working correctly and VM should be upgraded to the target cluster level version during the import. close?

Comment 2 Arik 2020-07-19 17:28:53 UTC

(In reply to Michal Skrivanek from comment #1)
> this should be working correctly and VM should be upgraded to the target
> cluster level version during the import. close?

Yeah, until the next time we break this flow...