Bug 989909 - [Neutron] Network name/ID is missing from error message when importing existing network ID on DC
Summary: [Neutron] Network name/ID is missing from error message when importing existi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: 3.3.0
Assignee: Lior Vernia
QA Contact: yeylon@redhat.com
URL:
Whiteboard: network
Depends On:
Blocks: 3.3snap2
TreeView+ depends on / blocked
 
Reported: 2013-07-30 07:12 UTC by Meni Yakove
Modified: 2016-02-10 19:50 UTC (History)
9 users (show)

Fixed In Version: is22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20604 0 'None' 'MERGED' 'webadmin: Allow different options for different entries' 2019-12-03 20:33:41 UTC
oVirt gerrit 20605 0 'None' 'MERGED' 'webadmin: Don''t display DCs that imported external network' 2019-12-03 20:33:41 UTC

Description Meni Yakove 2013-07-30 07:12:53 UTC
Description of problem:	
When importing neutron network with ID that already exist in the datacenter the network name/ID is missing in the error:

Error while executing action: Cannot add Network. The external network already exists as '${NetworkName}' in the data center.
 

Version-Release number of selected component (if applicable):
rhevm-3.3.0-0.11.master.el6ev.noarch

Steps to Reproduce:
1.Import network from neutron to DC1
2.Rename the imported network on DC1
3.import the same network from neutron to DC1

Actual results:
get '${NetworkName}' for network name/ID

Expected results:
Error should be with the network name/ID

Additional info:

Comment 1 Lior Vernia 2013-10-08 11:02:00 UTC
Fixed by simply not displaying DCs where the network had already been imported.

Comment 2 Lior Vernia 2013-11-10 08:42:08 UTC
Please note that the patch didn't fix the error message, but rather made it impossible to import a network to a DC where it exists. And now as I'm writing this, I'm thinking that there's probably a bug if the network had already been imported to all DCs :)

Comment 3 awinter 2013-11-17 11:10:55 UTC
Not fixed.

Now when I try to import a network with the same name as another network, I get:
"Error while executing action: User is not authorized to perform this action."

(Also when trying to add a network with existing vlan)

A bug for those messages was opened:
https://bugzilla.redhat.com/show_bug.cgi?id=1031366


(IS23 - Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.33.beta1.el6ev)


Lior - About your comments, now when a network is imported to all the DCs, the DC's drop box in the import pop up window is empty and small

Comment 4 Lior Vernia 2013-11-17 11:29:12 UTC
Amichay, what you're describing isn't a failure of the fix for this bug, it's the description of another bug. The bug here was about trying to import a network that had already existed in the DC (which is now impossible, because the only DCs shown are those where the network doesn't yet exist). You're talking about a network that has the same name as another network in the DC (but it's a different network).

Comment 5 awinter 2013-11-17 11:40:07 UTC
You are correct - sorry.

I thought you meant to write the name of the network in the error message but like you said, *it is not impossible to import a network twice to the same DC*

Comment 7 Itamar Heim 2014-01-21 22:32:09 UTC
Closing - RHEV 3.3 Released

Comment 8 Itamar Heim 2014-01-21 22:32:10 UTC
Closing - RHEV 3.3 Released


Note You need to log in before you can comment on or make changes to this bug.