Ask Your Question
0

br-ex-ln and br-fw-admin are not be created.

asked 2016-04-25 04:53:56 -0800

wu.zhihui gravatar image

I deployed OPNFV Brahmaputra + tun + odl-l2 by using fuel. The deployment was successful. Health check also was ok. My problem is why linux bridge br-ex-ln and br-fw-admin are not be created after rebooting one controller node. I found the same problem on two controller nodes of my env. How to troubleshoot this problem? Look forward to your reply.Thank you!

edit retag flag offensive close merge delete

Comments

Hi, could you please verify if inside /etc/network/interfaces.d/ directory ifcfg-br-ex-lnx and ifcfg-br-fw-admin files exist and contain definitions of theses bridges?

mskalski ( 2016-04-27 05:37:23 -0800 )edit

Thanks for your reply. I deployed my env again yesterday. The problem still exist. A little differencs is only br-fw-admin not created. According to your comments, I check /etc/network/interfaces.d/ directory. The file ifcfg-fw-admin exists.The returns of "brctl show" don't include br-fw-admin.

wu.zhihui ( 2016-04-27 21:01:38 -0800 )edit

Is there any logs I can check? If yes, could I send the logs to you by email? Thanks!

wu.zhihui ( 2016-04-27 21:03:54 -0800 )edit

Could you share content of ifcfg-br-fw-admin and ifcfg-br-ex-lnx files on some pastebin site? Output from 'hiera network_scheme' cmd can be also useful. Please also check if /var/log/upstart/network-interface-br-fw-admin.log file contain any information about problems with bringing up this bridge.

mskalski ( 2016-04-28 04:03:42 -0800 )edit

I send a email to you. There is a log which include content you mentioned. I also attach a screen capture when the node is powering on after reboot. There is a warning shown: unkonw attribute class/net/br-ex-lnx/queues/rx-0/rps_cpus; unkonw attribute class/net/br-ex-lnx/queues/tx-0/rps_cpus.

wu.zhihui ( 2016-05-03 19:54:07 -0800 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-05-04 13:16:03 -0800

mskalski gravatar image

In this deployment bonded interface is used for Public network. In that case bonded interface was assigned to br-ex ovs bridge but supposed to be added to br-ex-lnx linux bridge. This commit should change this behavior: https://review.openstack.org/#/c/312586/

This change will be cherry-picked to 8.0 branch of fuel opendaylight plugin so it will be possible to build plugin with this fix included. To patch already installed plugin you can edit /var/www/nailgun/plugins/opendaylight-0.8/deployment_scripts/puppet/modules/opendaylight/lib/puppet/parser/functions/odl_network_scheme.rb file on fuel master according to above change and redeploy environment.

Please check if after applying this patch you still observe problems.

edit flag offensive delete link more

Comments

Thanks! This solution worked. :) The odl_network_scheme.rb on local is a little different from yours. I only add the code "transformations.each { |action| action['bridge'] = 'br-ex-lnx' if (action['action'] == 'add-bond' and action['bridge'] == 'br-ex') }".

wu.zhihui ( 2016-05-06 18:23:45 -0800 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
1 follower

Stats

Asked: 2016-04-25 04:53:56 -0800

Seen: 441 times

Last updated: May 04 '16