Bug 1076909

Summary:	[Neutron integration] Network disappears and reappears in GUI when an action of removal of that network fails
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	GenadiC <gcheresh>
Component:	ovirt-engine	Assignee:	Moti Asayag <masayag>
Status:	CLOSED WONTFIX	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.4.0	CC:	acathrow, danken, gklein, iheim, lpeer, lvernia, nyechiel, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-17 07:38:21 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:	1063716

Description GenadiC 2014-03-16 12:12:36 UTC

Description of problem:
Network disappears from Network tab in GUI for a couple of seconds and reappears if an action of removal that networks fails

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


How reproducible:
Always

Steps to Reproduce:
1. Create Network in GUI for Rhev and Neutron provider
2. Remove that network from Neutron only
3.Try to remove that network from GUI when "Remove external network(s) from the provider(s) as well" checkbox is checked

Actual results:
Network disappears and reappears after couple of seconds in GUI

Expected results:
Network should be presented in GUI all the time as an action of removal failed

Additional info:

Comment 1 Dan Kenigsberg 2014-04-10 14:30:46 UTC

Effect is annoying, but should not be considered as a rhev-3.4.0 blocker.

Comment 2 Moti Asayag 2014-07-17 07:38:21 UTC

I've examined the alternatives for fixing the bug:

Reversing the order of the action to remove the network from the provider first and later on to delete it from the engine reveals more issues than expected: If the network is being removed from the provider successfully, but due to latency issue that action takes time, during that time the network might violate its state which was verified by the can-do-action validation.

Meaning, during the removal from the provider, other use might attach the network to its vm. An attempt to solve this hole requires too much work in compare to the benefit of having the network visible in the ui.

Without a better alternative of handling transactivity for an action spread between the ovirt-engine and the external provider, I'm closing this bug as "wontfix".