neutron-l3-agents won't become active
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Unassigned | ||
neutron (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
We have a Ubuntu Ussari cloud deployed on Ubuntu 20.04 using the juju charms from the 20.08 bundle (planning to upgrade soon).
The problem that is occuring that all l3 agents for routers using a particular external network show up with their ha_state in standby. I've tried removing and re-adding, and we never see the state go to active.
$ neutron l3-agent-
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
+------
| id | host | admin_state_up | alive | ha_state |
+------
| 09ae92c9-
| 4d9fe934-
| 70b8b60e-
+------
This generates a stack trace:
2021-03-01 02:59:47.344 3675486 ERROR neutron.
Traceback (most recent call last):
File "/usr/lib/
res = self.dispatcher
File "/usr/lib/
return self._do_
File "/usr/lib/
result = func(ctxt, **new_args)
File "/usr/lib/
setattr(e, '_RETRY_EXCEEDED', True)
File "/usr/lib/
self.
File "/usr/lib/
six.
File "/usr/lib/
raise value
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
ectxt.value = e.inner_exc
File "/usr/lib/
self.
File "/usr/lib/
six.
File "/usr/lib/
raise value
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
LOG.
File "/usr/lib/
self.
File "/usr/lib/
six.
File "/usr/lib/
raise value
File "/usr/lib/
return f(*dup_args, **dup_kwargs)
File "/usr/lib/
agent_port = self.l3plugin.
File "/usr/lib/
self.
File "/usr/lib/
network_ids = [p['network_id']
File "/usr/lib/
network_ids = [p['network_id']
File "/usr/lib/
fixed_ips = port.get(
This system was running successfully after deployment, and has been left running for a while and when it was revisited was in this state. I've been unable to successfully debug what has caused it to be in this state.
Versions:
Ubuntu 20.04
Juju charms 20.08
Openstack ussari
Environment: Clustered services using containers on converged hypervisors
$ dpkg-query -W neutron-common
neutron-common 2:16.2.0-0ubuntu2
Please let me know if there is any further information that could be used to see what is happening here.
Can You share with us Your full log from the neutron-server (where I assume this issue happened) and l3-agent?
Maybe You can also tell us what extension drivers are You using in Your neutron-l3-agent and what service-plugins do You have in neutron-server loaded.
Is that issue happening only for one router or for all routers which You have there?