Default value for Physical Network is hardcoded value

Bug #1417305 reported by Janet Yu
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Wishlist
Beth Elwell

Bug Description

The default value for the "Physical Network" field in the "Create Network" form of the Admin dashboard, shown when the Neutron provider extension is supported, is "default". It makes more sense for the default to be blank instead of a hardcoded string.

Janet Yu (jwy)
Changed in horizon:
assignee: nobody → Janet Yu (jwy)
Changed in horizon:
importance: Undecided → Wishlist
Beth Elwell (bethelwell)
Changed in horizon:
assignee: Janet Yu (jwy) → Beth Elwell (bethelwell)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/476453

Changed in horizon:
milestone: none → pike-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/476453
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=449aa1a48cc7260ffc3c78570334e9ee2fbc51cb
Submitter: Jenkins
Branch: master

commit 449aa1a48cc7260ffc3c78570334e9ee2fbc51cb
Author: Beth Elwell <email address hidden>
Date: Thu Jun 22 11:20:33 2017 +0100

    Removed default value for 'Physical Network'

    When creating a network there is currently a default value of 'default'
    which causes the network creation to fail. It is nonsensical to have
    a default value here as it will change depending on the provider
    network type and needs to be set according to custom settings if the
    user is not creating a simple local network which then does not require
    the physical network value at all.

    Change-Id: I448713d986f17ea1c00cd4dd22487291545cfe2a
    Closes-Bug: #1417305

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 12.0.0.0b3

This issue was fixed in the openstack/horizon 12.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.