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

Bug 1658095

Summary:	[core performance enhancement] - number of db calls on update of logical networks' status too large
Product:	[oVirt] ovirt-engine	Reporter:	eraviv
Component:	Backend.Core	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.8	CC:	bugs, mburman
Target Milestone:	ovirt-4.2.8	Keywords:	Performance
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ mburman: testing_plan_complete- mburman: testing_ack+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-22 10:23:08 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:

Description eraviv 2018-12-11 08:52:52 UTC

Description of problem:
while updating the network attachments status a db call is made for each network in the cluster separately. It can be reduced to a single call.

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


How reproducible:
100%

Steps to Reproduce:
1. create networks with attachment to cluster 
2. make the network non-operational and then operational
4. refresh network list in Compute > Clusters > clusterX > Logical networks
--> status should change

Actual results:
For a remote db and many networks the status update may take a while

Expected results:
status update should be fast


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2018-12-11 09:00:11 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Red Hat Bugzilla Rules Engine 2018-12-11 10:53:43 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Daniel Gur 2018-12-11 15:21:49 UTC

as this bug is petty simple 100% reproduced don't really need scale environment and performance engineer moving it back.

Comment 4 Michael Burman 2018-12-25 09:24:02 UTC

Verified on - 4.2.8.1-0.1.el7ev

Comment 5 Sandro Bonazzola 2019-01-22 10:23:08 UTC

This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.2.8 release, it has been closed with a resolution of CURRENT RELEASE.

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