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

Bug 1345810

Summary: [Neutron integration][webadmin] Subnet <UNKNOWN> was added on provider <UNKNOWN>
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: high    
Version: 4.0.0CC: bugs, danken, mmirecki, myakove, ylavi
Target Milestone: ovirt-4.0.6Flags: rule-engine: ovirt-4.0.z+
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
danken: devel_ack+
myakove: testing_ack+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 07:25:42 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:
Attachments:
Description Flags
screenshot none

Description Michael Burman 2016-06-13 08:54:55 UTC 
Created attachment 1167289 [details]
screenshot

Description of problem:
Subnet <UNKNOWN> was added on provider <UNKNOWN>. 

The subnet name and the provider name are unknown when creating network with subnet on the external provider via the engine.

Version-Release number of selected component (if applicable):
4.0.0.4-0.1.el7ev

How reproducible:
100

Steps to Reproduce:
1. Add external network provider to rhev-m(uncheck the 'read only' checkbox)
2. Create new network on the external network provider via the "Networks' main tab and check the 'Create on external provider' check box
3. Set subnet via the subnet sub tab on the left, enter name and valid CIDR and press 'ok' to approve operation

Actual results:
Subnet <UNKNOWN> was added on provider <UNKNOWN>.

Expected results:
Subnet <subnet name> was added on provider <provider name>.

Additional info:
See also - BZ 1216081
Comment 1 Michael Burman 2016-12-08 10:45:42 UTC 
Verified on - 4.0.6.2-0.1.el7ev
Comment 2 Marcin Mirecki 2017-05-26 15:00:21 UTC 
*** Bug 1320173 has been marked as a duplicate of this bug. ***