Bug 1428000

Summary:	Creating a public network from UI fails due to wrong default for 'Physical Network'
Product:	Red Hat OpenStack	Reporter:	Nenad Peric <nperic>
Component:	python-django-horizon	Assignee:	Beth White <beth.white>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	aortega, athomas, beth.white, mrunge, rdopiera, srevivo, tvignaud
Target Milestone:	beta	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-12.0.0-0.20170807210226.0a1a566.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 21:11:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nenad Peric 2017-03-01 16:46:05 UTC

Description of problem:

When trying to create an external network for a project, the creation fails with the Error: Failed to create network.

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

python-django-horizon-10.0.1-5.el7ost.noarch


How reproducible:
Everytime

Steps to Reproduce:

Go to Admin -> Networks -> Create Network
Fill in the fields, but leave the "Physical Network" as the offered "default" (which is invalid in the default OSP configuration)
Select the Shared and External Network checkboxes

Actual results:

The network is not created. 
An error is displayed but is not very helpful.

Expected results:

Ideally, the defaults presented by UI should align with the defaults of the OSP installation, and offer a proper entry in the forms.

If a wrong entry is given for the Physical Network, a more descriptive message would be helpful.
If the error message of the command, cannot be exposed, some advice can be given as to where the problem should be looked for, or which logs might have this information. 

Alternativelly, the form could have a tooltip saying where the valid value to "Physical Network" should come from (in this case the default is set in /etc/neutron/plugins/ml2/ml2_conf.ini. 

Additional info:

Comment 1 Beth White 2017-06-22 10:27:02 UTC

There is now a patch in review upstream. The solution we have come to is to remove the default value altogether and improve the tooltip information to include information for where to find and change physical network details to reduce confusion.

Comment 2 Beth White 2017-07-10 12:34:29 UTC

Due to there being multiple locations where the physical network details can be found depending on the plugin being used, ML2 being just one of many, the tooltip message has been amended to explain that physical networks are defined in your neutron deployment.

Comment 5 Radomir Dopieralski 2017-10-03 22:00:00 UTC

As per comment #2, there is no default value now, and the tooltip contains detailed explanation.

Comment 8 errata-xmlrpc 2017-12-13 21:11:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462