yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #46057
[Bug 1542923] Re: Linuxbridge agent failed to start when bridge_mappings is given
Reviewed: https://review.openstack.org/277611
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=034d5a2f374ec34fba31c2c322d2291a2fb00942
Submitter: Jenkins
Branch: master
commit 034d5a2f374ec34fba31c2c322d2291a2fb00942
Author: Slawek Kaplonski <slawek@xxxxxxxxxxxx>
Date: Tue Feb 9 00:35:05 2016 +0100
Fix getting agent id in linuxbridge agent
If bridge_mappings is configured in linuxbridge agent, it will now
determine agent_id which is based on MAC address of first device
from bridge_mappings in correct way.
Change-Id: I940379b2fd3b5f8c96cdf3b7a3c0da78532491f6
Closes-bug: #1542923
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1542923
Title:
Linuxbridge agent failed to start when bridge_mappings is given
Status in neutron:
Fix Released
Bug description:
When I was working on fullstack tests for Linuxbridge agent I found
that when bridge_mappings is configured in LinuxBridge agent config
file then for calculating agent_id mac address of first bridge name
from this bridge_mappings is searched and it is failing. Due to that
agent is not starting properly and is hanging.
Agent's log is stuck on:
ig/cfg.py:2405
2016-02-06 23:48:53.003 6023 DEBUG oslo_service.service [-] ******************************************************************************** log_opt_values /home/ubuntu/neutron/.tox/dsvm-fullstack/local/lib/python2.7/site-packages/oslo_con
fig/cfg.py:2407
2016-02-06 23:48:53.004 6023 DEBUG neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Init firewall settings (driver=None) init_firewall /home/ubuntu/neutron/neutron/agent/securitygroups_rpc.py:98
2016-02-06 23:48:53.005 6023 WARNING neutron.agent.securitygroups_rpc [req-43811efb-7a62-4059-8c93-b75b8554e7f8 - - - - -] Driver configuration doesn't match with enable_security_group
and then agent was not sending report about his state to neutron
server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1542923/+subscriptions
References