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

Bug 1431412

Summary:	Reduce number of transactions in commands that use NetworkClusterHelper.setStatus
Product:	[oVirt] ovirt-engine	Reporter:	Yevgeny Zaspitsky <yzaspits>
Component:	Backend.Core	Assignee:	Yevgeny Zaspitsky <yzaspits>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mor <mkalfon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0.6.3	CC:	bugs, lveyde, mkalfon
Target Milestone:	ovirt-4.1.2	Flags:	rule-engine: ovirt-4.1+
Target Release:	4.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:11:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1431228

Description Yevgeny Zaspitsky 2017-03-12 11:04:46 UTC

Description of problem:
The following commands use runInernalQuery mechanism, which suspends the current transaction and opens another one, in order to load host nics (GetVdsInterfacesByVdsId query):
* ActivateVdsCommand
* AttachNetworkToClusterInternalCommand
* HostSetupNetworksCommand
* MaintenanceNumberOfVdssCommand
* UpdateNetworkCommand
* UpdateNetworkOnClusterCommand
* UpdateVdsCommand

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


How reproducible:
100%

Actual results:
1. The running command 
2. Redundant additional transaction is open
3. If the parent transaction flow updated host nics in DB, running the query in a separate transaction will return results that aren't include those updates.

Expected results:
The commands should use the current transaction fo loading host nics.

Additional info:

Comment 1 Mor 2017-04-30 12:12:45 UTC

Verified on:
Red Hat Virtualization Manager Version: 4.1.2-0.1.el7

In order to verify it, I done the following steps:
1. Adding additional core (2 in total) on the engine VM to improve engine CPU time.
2. Setting up environment with 30 hosts and 50 hosts networks with VLAN attached to each of the hosts.
3. Setting up Power Management agent on each of the 50 hosts.
4. Changing host comment.
5. Editing existing host network and changing IP address settings.
6. Removing and adding host networks from specific host.