Bug 1048752

Summary: [Neutron integration] The message is not descriptive enough on failure of importing the network
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: ovirt-engine-webadmin-portalAssignee: Lior Vernia <lvernia>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: medium    
Version: 3.3.0CC: bazulay, danken, ecohen, eedri, iheim, lpeer, masayag, myakove, nyechiel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: vt2.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:15:12 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, 1142923, 1156165    

Description GenadiC 2014-01-06 10:00:31 UTC
Description of problem:
If the import of Network from Provider fails for some reason you get the message: "Cannot import the network" without specifying which network failed on import action

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


How reproducible:
Always

Steps to Reproduce:
1. Create 2 networks with the same name on External Network provider
2. Try to import them to RHEVM
3.

Actual results:
The network that failed on import action is not specified in the Error message

Expected results:
Error message should be descriptive enough to understand which network caused the failure

Additional info:

Comment 1 Dan Kenigsberg 2014-05-08 07:36:45 UTC
This bug is not a blocker or an exception forand won't make it for 3.4.0.

Comment 2 GenadiC 2014-07-03 12:31:58 UTC
The message provided makes sense when trying to import the network with the name already existing in RHEV, but if you import 2 networks with the same name it's not that clear.

As a discussed proposal for that it will make sense to check if we have redundant names for imported networks and inform user to rename the Network

Comment 4 Michael Burman 2014-09-07 13:54:25 UTC
Verified on - 3.5.0-0.10.master.el6ev

Comment 5 Eyal Edri 2015-02-17 17:15:12 UTC
rhev 3.5.0 was released. closing.