yahoo-eng-team team mailing list archive

[YG Kumar <ygk.kmr@xxxxxxxxx>]

Public bug reported:

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-list-hosting-router" .

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 '7ec2fa3057374a1584418124d5b879ca':

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_thread_pool_size = 64
fatal_deprecations = False
l3_ha = False
log_file = /var/log/neutron/neutron.log
rpc_response_timeout = 60
transport_url = rabbit://neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.236.201:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.27:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.39:5671//neutron?ssl=1
# Disable stderr logging
use_stderr = False

# Agent
[agent]
polling_interval = 5
report_interval = 60
root_helper = sudo /openstack/venvs/neutron-18.1.4/bin/neutron-rootwrap /etc/neutron/rootwrap.conf

# Concurrency (locking mechanisms)
[oslo_concurrency]
lock_path = /var/lock/neutron

# Notifications
[oslo_messaging_notifications]
driver = messagingv2
notification_topics = notifications,notifications_designate
transport_url = rabbit://neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.236.201:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.27:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.39:5671//neutron?ssl=1

# Messaging
[oslo_messaging_rabbit]
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_l3agent_failover = True

# HA failover
ha_confs_path = /var/lib/neutron/ha_confs
ha_vrrp_advert_int = 2
ha_vrrp_auth_password = ec86ebf62a85f387569ed0251dc7c8dd9e484949ba320a6ee6bf483758a318
ha_vrrp_auth_type = PASS

# Metadata
enable_metadata_proxy = True

# L3 plugins
------------------------ 


Please help us with this issue.

Thanks
Y.G Kumar

** 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/1823023

Title:
  l3 namespaces

Status in neutron:
  New

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-list-hosting-router" .

  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 '7ec2fa3057374a1584418124d5b879ca':

  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_thread_pool_size = 64
  fatal_deprecations = False
  l3_ha = False
  log_file = /var/log/neutron/neutron.log
  rpc_response_timeout = 60
  transport_url = rabbit://neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.236.201:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.27:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.39:5671//neutron?ssl=1
  # Disable stderr logging
  use_stderr = False

  # Agent
  [agent]
  polling_interval = 5
  report_interval = 60
  root_helper = sudo /openstack/venvs/neutron-18.1.4/bin/neutron-rootwrap /etc/neutron/rootwrap.conf

  # Concurrency (locking mechanisms)
  [oslo_concurrency]
  lock_path = /var/lock/neutron

  # Notifications
  [oslo_messaging_notifications]
  driver = messagingv2
  notification_topics = notifications,notifications_designate
  transport_url = rabbit://neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.236.201:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.27:5671,neutron:6a5c9d9634190b954f133f274d793be4d2@172.29.239.39:5671//neutron?ssl=1

  # Messaging
  [oslo_messaging_rabbit]
  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_l3agent_failover = True

  # HA failover
  ha_confs_path = /var/lib/neutron/ha_confs
  ha_vrrp_advert_int = 2
  ha_vrrp_auth_password = ec86ebf62a85f387569ed0251dc7c8dd9e484949ba320a6ee6bf483758a318
  ha_vrrp_auth_type = PASS

  # Metadata
  enable_metadata_proxy = True

  # L3 plugins
  ------------------------ 

  
  Please help us with this issue.

  Thanks
  Y.G Kumar

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1823023/+subscriptions