Bug 1340628

Summary:	[downsream clone - 3.6.7] HE Vm's ovf isn't updated according to 'OvfUpdateIntervalInMinutes' value
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED ERRATA	QA Contact:	sefi litmanovich <slitmano>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.5	CC:	alukiano, amarchuk, bgraveno, bugs, danken, dfediuck, lsurette, mavital, mgoldboi, mkalinin, rbalakri, rgolan, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	ovirt-3.6.7	Keywords:	ZStream
Target Release:	3.6.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Virtual machines are backed up periodically if the version field changes since the last backup. However, because modifying the virtual machine vNic does not update the version field, virtual machine definitions do not get backed up if only a vNic change occurs. This update ensures that a vNic update will cause virtual machine definitions to be backed up.	Story Points:	---
Clone Of:	1327267	Environment:
Last Closed:	2016-06-29 16:20:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1327267
Bug Blocks:

Comment 3 sefi litmanovich 2016-06-07 15:24:57 UTC

Verified with:
ENGINE:
rhevm-3.6.7.2-0.1.el6.noarch
HOST: 
ovirt-hosted-engine-ha-1.3.5.7-1.el7ev.noarch
vdsm-4.17.30-1.el7ev.noarch

Followed steps from my description of the bug,
This time after adding the nic to the HostedEngine vm, the nic appeared in vm's xml (both with dumpxml from virsh and in host's agent.log).
Also verified that the nic is not unplugged after shutting the vm down and re starting it.

Comment 4 Marina Kalinin 2016-06-24 22:04:22 UTC

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

Comment 8 errata-xmlrpc 2016-06-29 16:20:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2016:1364