The public network cannot be identified by df-local-controller

Bug #1657705 reported by Li Ma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DragonFlow
Fix Released
High
Hong Hui Xiao

Bug Description

2017-01-17 15:48:44.030 6379 ERROR dragonflow.controller.l2_app [-] Physical network public unknown for dragonflow

This message is shown in fullstack job of CI.

For example:
http://logs.openstack.org/02/420602/4/check/gate-dragonflow-dsvm-fullstack-ubuntu-xenial/6521011/logs/screen-df-controller.txt.gz

Li Ma (nick-ma-z)
Changed in dragonflow:
importance: Undecided → High
Revision history for this message
Hong Hui Xiao (xiaohhui) wrote :

Since we are only support one external network for now, we can just create/manage it in advance. No need to create and then delete external network every time.

Changed in dragonflow:
assignee: nobody → Hong Hui Xiao (xiaohhui)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to dragonflow (master)

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

Changed in dragonflow:
status: New → In Progress
Revision history for this message
Hong Hui Xiao (xiaohhui) wrote :

Since the bridge_mapping will have a default value ['public:br-ex'], the issue has gone with it.

https://github.com/openstack/dragonflow/blob/d692596b5d29c3bc852bfa996e5a5874ff745581/dragonflow/conf/df_provider_networks.py#L23

Changed in dragonflow:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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