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

Bug 1505421

Summary:	DR (site to site) - Support affinity label related to a VM as part of the VM's OVF
Product:	[oVirt] ovirt-engine	Reporter:	Maor <mlipchuk>
Component:	Backend.Core	Assignee:	Maor <mlipchuk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Elad <ebenahar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	amureini, bugs, ratamir, tnisan
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
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-12-20 11:32:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maor 2017-10-23 14:33:18 UTC

Description of problem:
The VM's OVF should include affinity labels related to a VM. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Add affinity label
2. Detach a storage domain
3. attach the storage domain back again
4. Import the VM again

Actual results:


Expected results:
The affinity label should be assigned to the VM

Additional info:

Comment 1 Tal Nisan 2017-10-24 10:22:08 UTC

*** Bug 1505422 has been marked as a duplicate of this bug. ***

Comment 2 Maor 2017-11-29 00:05:11 UTC

The closed bug BZ1505422 got me confused.
the affinity label should already be integrated in the VM's OVF.
Therefore moving to ON_QA

Comment 3 Elad 2017-12-17 17:29:19 UTC

1. Add affinity label
2. Detach a storage domain
3. attach the storage domain back again
4. Import the VM again

VM has the affinity label assigned after registration.


Used:
rhvm-4.2.0.2-0.1.el7.noarch

Comment 4 Sandro Bonazzola 2017-12-20 11:32:22 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.