legacy router namespaces absence or error run exec
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Undecided
|
Unassigned | ||
neutron |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Hi,
We have a rocky OSA setup 18.1.4 version from git. Whenever we create a router it is getting created and showing a compute node as host with the command "l3-agent-
But when we log into the compute node and check, there is no namespace for that router and sometimes
even though that namespace is created, when we do a ip netns exec qrouter-xxxxxxxxx ip a
that throws an error "Unable to find router with name or id '7ec2fa3057374a
Also when we do a ip netns on the computes we see this :
---------
Error: Peer netns reference is invalid.
Error: Peer netns reference is invalid.
-------------
The neutron.conf file on the computes:
----------
# Ansible managed
# General, applies to all host groups
[DEFAULT]
debug = True
# Domain to use for building hostnames
dns_domain = vbg.example.cloud
## Rpc all
executor_
fatal_deprecations = False
l3_ha = False
log_file = /var/log/
rpc_response_
transport_url = rabbit:
# Disable stderr logging
use_stderr = False
# Agent
[agent]
polling_interval = 5
report_interval = 60
root_helper = sudo /openstack/
# Concurrency (locking mechanisms)
[oslo_concurrency]
lock_path = /var/lock/neutron
# Notifications
[oslo_messaging
driver = messagingv2
notification_topics = notifications,
transport_url = rabbit:
# Messaging
[oslo_messaging
rpc_conn_pool_size = 30
ssl = True
------------------
l3_agent.ini file
------------
# Ansible managed
# General
[DEFAULT]
debug = True
# Drivers
interface_driver = openvswitch
agent_mode = legacy
# Conventional failover
allow_automatic
# HA failover
ha_confs_path = /var/lib/
ha_vrrp_advert_int = 2
ha_vrrp_
ha_vrrp_auth_type = PASS
# Metadata
enable_
# L3 plugins
-------
Please help us with this issue.
Thanks
Y.G Kumar
summary: |
- l3 namespaces + legacy router namespaces absence or error run exec |
Hi,
I observed this when I try to create a network namespace manually on the compute nodes. The below command is hanging and never completes:
--------------
ip netns add test