[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
Dr. Jens Harbott
j.harbott at x-ion.de
Tue May 8 21:04:42 UTC 2018
@David: I have not been able to reproduce the error on xenial with
queens UCA. Your logs look like you are running without the patch
applied. Can you doublecheck that you did install the patched packages?
Can you set "debug=true" in /etc/neutron/bgp_dragent.ini and post logs
from that?
>From my POV the pkg works as expected, so I'd set "verification-queens-
done" but I don't want to override your report without your feedback.
I'll do another test on bionic tomorrow.
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker to agent fails
Status in Ubuntu Cloud Archive:
Fix Committed
Status in Ubuntu Cloud Archive pike series:
Fix Committed
Status in Ubuntu Cloud Archive queens series:
Fix Committed
Status in neutron:
Fix Released
Status in neutron-dynamic-routing package in Ubuntu:
Fix Released
Status in neutron-dynamic-routing source package in Artful:
Fix Committed
Status in neutron-dynamic-routing source package in Bionic:
Fix Committed
Status in neutron-dynamic-routing source package in Cosmic:
Fix Released
Bug description:
SRU details for Ubuntu
----------------------
[Impact]
See "Original description" below.
[Test Case]
See "Original description" below.
[Regression Potential]
Low. This is fixed upstream in corresponding stable branches.
Original description
--------------------
When following https://docs.openstack.org/neutron-dynamic-routing/latest/contributor/testing.html everything works fine because the speaker is scheduled to the agent automatically (in contrast to what the docs say). But if I remove the speaker from the agent and add it again with
$ neutron bgp-dragent-speaker-remove 0159fc0a-22de-4995-8fad-8fb8835a4d86 bgp-speaker
$ neutron bgp-dragent-speaker-add 0159fc0a-22de-4995-8fad-8fb8835a4d86 bgp-speaker
the following error is seen in the log:
Feb 17 10:56:30 test-node01 neutron-bgp-dragent[18999]: ERROR
neutron_dynamic_routing.services.bgp.agent.bgp_dragent [None req-
da9a22ae-52a2-4be7-a3e8-2dc2dc970fdd admin admin] Call to driver for
BGP Speaker d2aa5935-30c2-4369-83ee-b3a0ff77cc49 add_bgp_peer has
failed with exception 'auth_type'.
The same thing happens when there are multiple agents and one tries to
add the speaker to one of the other agents.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1750121/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list