Bug 1254320

Summary:	[New HostSetupNetworks] if no changes were done- setup networks shouldn't be invoked
Product:	[oVirt] ovirt-engine	Reporter:	Alona Kaplan <alkaplan>
Component:	General	Assignee:	Martin Mucha <mmucha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	low
Version:	---	CC:	bugs, danken, ecohen, gklein, lsurette, rbalakri, yeylon, ylavi
Target Milestone:	ovirt-3.6.2	Flags:	danken: ovirt-3.6.z? ylavi: planning_ack+ danken: devel_ack+ ylavi: testing_ack?
Target Release:	3.6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-13 15:42:37 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 Alona Kaplan 2015-08-17 17:19:38 UTC

Description of problem:

If the updated attachment/bond is identical to the original one- setup networks should ignore it.

This fix will fix the following bugs-
1. Opening the edit dialog of "out-of-sync" network and clicking ok-> then clicking ok in the setup networks window.
Since the ui adds the attachment to the params even if no change was done- the result is- can do action of "editing out-of-sync network is not permitted". Although no change was done.

Fixing the engine side should be enough. The engine should ignore this attachment.

2. Sending setup networks command with the existing attachments/bonds as the parameters. Result- setup network is invoked on the host although no changes are needed. 



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 11:00:17 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 2015-10-26 16:56:23 UTC

This request has been proposed for two releases. This is invalid flag usage. The higher numbered release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 3 Yaniv Lavi 2015-10-29 12:30:03 UTC

In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.

Comment 4 Sandro Bonazzola 2015-12-23 13:42:27 UTC

oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA

Comment 5 Pavel Stehlik 2016-01-13 15:42:37 UTC

Closing old bugs. In case still happens, pls reopen.