Bug 1428000 - Creating a public network from UI fails due to wrong default for 'Physical Network'
Summary: Creating a public network from UI fails due to wrong default for 'Physical Ne...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 12.0 (Pike)
Assignee: Beth White
QA Contact: Ido Ovadia
Depends On:
TreeView+ depends on / blocked
Reported: 2017-03-01 16:46 UTC by Nenad Peric
Modified: 2018-02-05 19:04 UTC (History)
7 users (show)

Fixed In Version: python-django-horizon-12.0.0-0.20170807210226.0a1a566.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:11:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1417305 0 None None None 2017-06-08 08:28:12 UTC
OpenStack gerrit 476453 0 None MERGED Removed default value for 'Physical Network' 2020-02-10 07:00:09 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):


How reproducible:

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.


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