yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #71209
[Bug 1750121] [NEW] Dynamic routing: adding speaker to agent fails
Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker to agent fails
Status in neutron:
New
Bug 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/neutron/+bug/1750121/+subscriptions
Follow ups
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Dr. Jens Harbott, 2019-12-20
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-06-25
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-06-25
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-06-14
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Launchpad Bug Tracker, 2018-06-13
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Launchpad Bug Tracker, 2018-05-03
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-05-03
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-04-25
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-04-25
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: Corey Bryant, 2018-04-25
-
[Bug 1750121] Re: Dynamic routing: adding speaker to agent fails
From: OpenStack Infra, 2018-03-22