** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
** Changed in: cloud-archive/pike
Status: New => Triaged
** Changed in: cloud-archive/queens
Status: New => Triaged
** Changed in: cloud-archive/pike
Importance: Undecided => High
** Changed in: cloud-archive/queens
Importance: Undecided => High
** No longer affects: neutron (Ubuntu)
** Also affects: neutron-dynamic-routing (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron-dynamic-routing (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: neutron-dynamic-routing (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: neutron-dynamic-routing (Ubuntu Artful)
Status: New => Triaged
** Changed in: neutron-dynamic-routing (Ubuntu Artful)
Importance: Undecided => High
** Changed in: neutron-dynamic-routing (Ubuntu Bionic)
Status: New => Triaged
** Changed in: neutron-dynamic-routing (Ubuntu Bionic)
Importance: Undecided => High
** Description changed:
- 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
+ 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.
--
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 Ubuntu Cloud Archive:
Triaged
Status in Ubuntu Cloud Archive pike series:
Triaged
Status in Ubuntu Cloud Archive queens series:
Triaged
Status in neutron:
Fix Released
Status in neutron-dynamic-routing package in Ubuntu:
Triaged
Status in neutron-dynamic-routing source package in Artful:
Triaged
Status in neutron-dynamic-routing source package in Bionic:
Triaged
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
