No router namespace after creating legacy router

Bug #1529820 reported by Kristina Berezovskaia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
Medium
Inessa Vasilevskaya
8.0.x
Won't Fix
Medium
Oleg Bondarev
9.x
Won't Fix
Medium
Inessa Vasilevskaya

Bug Description

After creating legacy router there are no router namespace on all controllers.

In neutron server log we can see:
2015-12-28 15:13:31.396 2490 DEBUG neutron.scheduler.l3_agent_scheduler [req-12d0d02c-8357-416e-9031-ae977493a739 35621d0df7ab45f3913905688e07abe6 edd49e6578a14d4f91e0262ba13382e8 - - -] Router 0f623aac-77a4-438a-b1a3-19b508f2aa58 is scheduled to L3 agent 16b37f34-4dc9-4f52-8ec4-253ddd1d2f6e bind_router /usr/lib/python2.7/dist-packages/neutron/scheduler/l3_agent_scheduler.py:227
2015-12-28 15:13:31.408 2490 DEBUG neutron.api.rpc.agentnotifiers.l3_rpc_agent_api [req-12d0d02c-8357-416e-9031-ae977493a739 35621d0df7ab45f3913905688e07abe6 edd49e6578a14d4f91e0262ba13382e8 - - -] Notify agent at l3_agent.node-5.domain.tld the message routers_updated _agent_notification /usr/lib/python2.7/dist-packages/neutron/api/rpc/agentnotifiers/l3_rpc_agent_api.py:70
2015-12-28 15:13:31.410 2490 DEBUG oslo_messaging._drivers.amqpdriver [req-12d0d02c-8357-416e-9031-ae977493a739 35621d0df7ab45f3913905688e07abe6 edd49e6578a14d4f91e0262ba13382e8 - - -] CAST unique_id: 3463b5625e5b492683ecc91d3f27f802 exchange 'neutron' topic 'l3_agent' _send /usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py:479

But this information didn't mentioned in l3-agent log

Steps:
run script
neutron net-create net_EW_1
neutron subnet-create --name net_EW_1__subnet net_EW_1 10.1.1.0/24

neutron net-create net_EW_2
neutron subnet-create --name net_EW_2__subnet net_EW_2 10.1.2.0/24

neutron router-create --distributed False router_EW
neutron router-gateway-set router_EW admin_floating_net
neutron router-interface-add router_EW net_EW_2__subnet
neutron router-interface-add router_EW net_EW_1__subnet

NODE_1="node-4.domain.tld"
NODE_2="node-7.domain.tld"

NET_ID_1=$(neutron net-list | grep net_EW_1 | awk '{print$2}')
nova boot vm_EW_1 --flavor 1 --image TestVM --availability-zone nova:$NODE_1 --nic net-id=$NET_ID_1

NET_ID_2=$(neutron net-list | grep net_EW_2 | awk '{print$2}')
nova boot vm_EW_2 --flavor 1 --image TestVM --availability-zone nova:$NODE_2 --nic net-id=$NET_ID_2

After this script there are no qrouter-namespace on controllers

Find on:
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "361"
  build_id: "361"
  fuel-nailgun_sha: "53c72a9600158bea873eec2af1322a716e079ea0"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "7463551bc74841d1049869aaee777634fb0e5149"
  fuel-nailgun-agent_sha: "92ebd5ade6fab60897761bfa084aefc320bff246"
  astute_sha: "c7ca63a49216744e0bfdfff5cb527556aad2e2a5"
  fuel-library_sha: "ba8063d34ff6419bddf2a82b1de1f37108d96082"
  fuel-ostf_sha: "889ddb0f1a4fa5f839fd4ea0c0017a3c181aa0c1"
  fuel-mirror_sha: "8adb10618bb72bb36bb018386d329b494b036573"
  fuelmenu_sha: "824f6d3ebdc10daf2f7195c82a8ca66da5abee99"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "9f0ba4577915ce1e77f5dc9c639a5ef66ca45896"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "07d5f1c3e1b352cb713852a3a96022ddb8fe2676"

Attach all logs

Tags: area-neutron
Revision history for this message
Kristina Berezovskaia (kkuznetsova) wrote :
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Neutron team, what is the user impact of this? Maybe this should be raised to High?

Changed in mos:
status: New → Confirmed
tags: added: area-neutron
removed: neutron
Revision history for this message
Alexander Ignatov (aignatov) wrote :

Rare issue, won't fix for 8.0 as it's Medium.

Revision history for this message
Oleg Bondarev (obondarev) wrote :

This is a rare case when when rpc message was lost for some reason: cast went from neutron server but nothing was received by the agent. The fix on neutron side could be to use rpc call() to ensure messages are delivered to agents. IMO not High. User impact: newly created router is not created by the agent, when adding interface or any other router update things should get back to normal.

Revision history for this message
Kristina Berezovskaia (kkuznetsova) wrote :
Changed in mos:
status: Confirmed → Won't Fix
Revision history for this message
Inessa Vasilevskaya (ivasilevskaya) wrote :

Spent a day trying to reproduce - with no success. The solution (as Oleg Bondarev has proposed) could be to use call instead of cast in routers_updated method, but I feel a bit uncomfortable proposing a fix on an issue I didn't face personally.

I'll add a link to a similar issue (fixed by Oleg Bondarev earlier) just for the sake of completeness - https://bugs.launchpad.net/mos/+bug/1481739.

Revision history for this message
Alexander Ignatov (aignatov) wrote :

As per discussion with Inessa and Oleg this bug is being moved to 10.0 since it has too many patches to be fixed and this is almost about refactoring.

Revision history for this message
Inessa Vasilevskaya (ivasilevskaya) wrote :

The fix will come in 2 upstream patches: https://review.openstack.org/#/c/302335/ (the refactor part) and https://review.openstack.org/#/c/303823/ (the bugfix itself).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.