*** This bug is a duplicate of bug 1845557 ***
https://bugs.launchpad.net/bugs/1845557
This bug is also a duplicate of
https://bugs.launchpad.net/neutron/+bug/1845557
** This bug is no longer a duplicate of bug 1715395
FWaaS: Firewall creation fails in case of distributed routers (Pike)
**
VM is not protected by the Firewall rules.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: Confirmed
** Tags: fwaas l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) => Swaminathan Vasudevan (swamina
** Changed in: neutron
Status: New => Opinion
** Changed in: neutron
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1840979
Title:
[L2] [opin
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1824571
Title:
l3agent can't create router if there are multiple external n
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1824566
Title:
DVR-Nexthop static routes are not getting configured in
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1823314
Title:
ha router sometime goes in standby mode in all controllers
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1815676
Title:
DVR: External process monitor for keepalived should be removed
Public bug reported:
Nexthop static routes for external network are not getting configured in the
FIP Namespace table, after disassociating and re-associating a FloatingIP.
This is seen in Ocata and Newton. Not seen in Pike and later branches.
Steps to reproduce this problem.
1. Deploy the devst
Public bug reported:
Some Gate jobs are failing for stable/ocata, is there any known issues
with the stable/ocata branch.
See the patch for details.
https://review.openstack.org/#/c/640176/
https://review.openstack.org/#/c/642363/
** Affects: neutron
Importance: Undecided
Status: N
Public bug reported:
Removing an active or a standby ha-router from an agent, does not clear the
router namespace and the Snat namespaces.
This leads to sometimes having two Active HA routers and two 'ha-interface' in
the snat namespace for DVR routers.
This can be very easily reproduced.
1. Cr
Public bug reported:
External process monitor for keepalived state change should be removed when the
External Gateway is removed for DVR HA routers.
We have seen under certain conditions when the SNAT namespace is missing, the
External process Monitor is try to respawn the keepalived state chang
Public bug reported:
Probably we have a problem with SNAT, with too many connections using the same
source / destination, on the network nodes.
We have reproduced the bug with DNS requests, but we assume that it affects
other packages as well.
When we send a lot of DNS requests, we see that
So if i understand your recommendation are you suggesting that we
completely ignore the HOST MAC change that we make today and just use
VLAN+MAC learning, so that the packets will get out of the host with its
own MAC.
What will happen to the switch learning that would happen in the
intermediate ph
** Changed in: neutron
Status: In Progress => Confirmed
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1606741
Title:
Public bug reported:
When DVR routers are configured for HA and if we try to add an extra
route to the DVR routers, the extra route is not set in the router
namespace or in the snat namespace.
Configure for HA and DVR
1. Create Router
2. Attach Interface
3. Try to add an extra route with destinat
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1716782
Title:
DVR multinode job has linuxbridge agent mech driver defi
Public bug reported:
When we configure two or more lbaas haproxy agents with high
availability by setting the allow_automatic_lbaas_agent_failover to
True for failover, then the LBaaS fails over to an available active
agent, either when the agent is not responsive or the agent lost
connection wit
Public bug reported:
When external bridge is configured in Neutron, the FIP Agent Gateway
port 'fg-' is tagged as a DEAD port with Vlan id of 4095.
This issue is seen in Pike.
It seems that there was fix that recently merged in neutron shown below
https://review.openstack.org/#/c/564825/10
Base
Public bug reported:
Sometimes we have seen the 'fg' ports within the fip-namespace either goes
down, not created in time or getting deleted due to some race conditions.
When this happens, the code tries to recover itself after couple of exceptions
when there is a router_update message.
But aft
Public bug reported:
FloatingIP create throws an error if the L3 agent is not running on the given
host for DVR Routers.
This can be reproduced by
1. Configure the global router settings to be 'Legacy' CVR routers.
2. Then configure a DVR Router by manually setting '--distributed = True' from
CL
Public bug reported:
This RFE is to add support for IPv6 on DVR Routers for the Fast-Path-Exit.
Today DVR support Fast-Path-Exit through the FIP Namespace, but FIP Namespace
does not support IPv6 addresses for the Link local address and also we don't
have any ra proxy enabled in the FIP Namespac
Public bug reported:
We have a long term issue with Allowed_address_pairs IP which associated with
unbound ports and DVR routers.
The ARP entry for the allowed_address_pair IP does not change based on the GARP
issued by any keepalived instance.
Since DVR does the ARP table update through the co
Public bug reported:
PCI-Passthrough of a NIC device to the VM fails, when we have both the
Flavor configured with Alias and also provide a network port with
'vnic_type=direct-physical'.
The comment shown in the source code shown below,
https://github.com/openstack/nova/blob/644ac5ec37903b0a088
Public bug reported:
As per the documentation shown below
https://docs.openstack.org/nova/pike/admin/pci-passthrough.html
In order to achieve PCI passthrough of a network device, it states that
we should create a 'flavor' based on the alias and then associate a
flavor to the server create functi
Public bug reported:
We have seen this Traceback in Pike based installation, while trying to
cleanup a gateway with DVR routers.
2018-04-03 20:30:10.081 9672 DEBUG neutron.agent.l3.dvr_fip_ns [-] Delete FIP
link interfaces for router: e415276a-4f37-4ee0-ba48-12d3909153c7
delete_rtr_2_fip_link
*** This bug is a duplicate of bug 1753540 ***
https://bugs.launchpad.net/bugs/1753540
Cherry-picked to stable/pike
https://review.openstack.org/#/c/557536/
** This bug has been marked a duplicate of bug 1753540
When isolated metadata is enabled, metadata proxy doesn't get automatically
s
Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1758093
Title:
DVR:
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1757188
Title:
some L3 HA routers does not work
Status in neutron:
Invalid
Bug des
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: neutron
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1757495
Title:
Using
ed to add a patch to change the
format of the MAC before it is handed over to the openflow interface driver.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
--
You received this
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1657981
Title:
FloatingIPs not reachable after restart of compute node (DVR)
Status i
*** This bug is a duplicate of bug 1715395 ***
https://bugs.launchpad.net/bugs/1715395
** This bug is no longer a duplicate of bug 1716401
FWaaS: Ip tables rules do not get updated in case of distributed virtual
routers (DVR)
** This bug has been marked a duplicate of bug 1715395
FWaaS:
Public bug reported:
Inter Tenant Traffic between Two Tenants on two different private
networks connected through a common shared network (created by Admin) is
not route able through DVR routers
Steps to reproduce it:
(NOTE: No external, just shared network)
This is only reproducable in Multinod
User error.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1749577
Title:
DVR: Static routes are not configured in snat-namespase fo
Public bug reported:
Static routes are not configured in snat-namespace for DVR routers.
Steps to reproduce:
1. Create Network
2. Create Subnet
3. Create Router
4. Add interface to Router
5. Set gateway for the Router
6. Add a static route (next hop to the Router)
7. Go check the 'snat-namespace'
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1667877
Title:
[RFE] Allow DVR for E/W while leaving N/S centralized
S
In that case we should close this bug.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1635554
Title:
Delete Router / race co
Right now there is no bug fixes are support for mitaka branch. Since
this bug is not seen in the current master and stable branch, so I would
close this bug.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engin
is not seen on the host where the VM resides.
Theoretically the FloatingIP should be migrated to the host where it is
currently bound.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: Confirmed
** Tags: l3-dvr-backlog
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1718585
Title:
set floatingip status to DOWN during creation
Status in neutron:
Opi
Public bug reported:
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSameNetwork and
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSeparateNetwork are
failing on every patch.
This trace is seen on the node-2 l3-agent.
Sep 13 07:16:43.404250 ubuntu-xenial-2-node-rax-dfw-10909
ecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
** Changed in: neutron
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
Public bug reported:
get_router_cidrs over-ridden in dvr_edge_router is not returing the
centralized_floating_ip cidrs.
So the consequence is the DNAT rules are left over in the snat namespace when
the centralized_floating_ips are removed.
** Affects: neutron
Importance: Undecided
Public bug reported:
When there is a DVR router with gateway enabled, and if the agent
restarts, then the router_update fails and you can see Error log in the
l3_agent.log.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status
the
error.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: Confirmed
** Tags: l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) => Swaminathan Vasudevan (swaminathan-vasudevan)
** Changed in: neutron
Public bug reported:
At large scale testing when trying to deploy around 8000 VMs with DVR
routers, we are seeing an RPC Timeout error in ovs_neutron_agent.
This RPC Timeout error occurs when the ovs_neutron_agent tries to bind the vif
port.
On further analysis it seems that the update_port_stat
em.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: Confirmed
** Tags: l3-dvr-backlog
** Tags added: l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) => Swaminathan Vasudevan (swaminathan-vasudevan)
Public bug reported:
Provide a Configurable option to configure Floatingips for DVR based routers to
reside on Compute Node or on Network Node.
Also proactively check the status of the agent on the destination node and if
the agent health is down, then configure the Floatingip on the Network Nod
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1524020
Title:
DVRImpact: dvr_vmarp_table_update and dvr_update_router
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1554876
Title:
router not found warning logs in the L3 agent
Status in
Public bug reported:
There seems to be a race condition when trying to add default gateway
route in fip namespace for the fip agent gateway port.
The way it happens is at high scale testing, when there is a router
update that is currently happening for the Router-A which has a
floatingip, a fip n
I did verify it in Mitaka and I don't see any issues with the 'sg' port
and related rules with respect to failover.
So we can close this issue as we discussed last week.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
VPN is a centralized service and not distributed one. The VPN service is only
running in the SNAT Namespace and not on the router or fip namespace.
So the fip traffic flowing through the fip namespace or router namespace may
not go through the IPsec driver that is running in SNAT Namespace.
This
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1609217
Title:
DVR: dvr router should not exist in not-binded network node
St
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1614337
Title:
L3 agent fails on FIP when DVR and HA both enabled in router
Sta
Public bug reported:
SNAT redirect rules should be removed only on Gateway clear and not for a
gateway move or gateway reschedule.
This would cause the snat_node unreachable by the dvr service ports on the
originating node.
How to reproduce it.
1. Create a two network node setup (dvr_snat)
2.
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
** Summary changed:
- ip_lib: Add support for 'Flush' command for iproute
+ ip_lib: Add support for 'Flush' command in iproute
--
You received thi
the local file system and reused later when necessary.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
** Tags added: l3-dvr-backlog
--
You received this bug notification because
Public bug reported:
DVR support for Allowed_address_pair ports with FloatingIP that are
unbound and assgined to Multiple VMs that are active.
Problem Statement:
When FloatingIP is asssigned to Allowed_address_pair port and assigned to
multiple VMs that are ACTIVE and connected to DVR (Distribu
** Also 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/1578866
Title:
test_user_update_own_password failing intermittently
S
Public bug reported:
Allowed_address_pair fixed_ip when configured with FloatingIP after the
port is associated with the VM port is not reachable from DVR router.
The current code only supports adding in the proper ARP update and port
host binding inheritence for the Allowed_address_pair port onl
see this in the neutron-server logs.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: New
** Tags: l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) => Swaminathan Vasudevan (swaminathan-vasu
Public bug reported:
Check for snat_namespace existence in the node before any operation
in the namespace.
Today we check the self.snatnamespace which may or may not reflect
the exact state of the system.
If the snat_namespace is accidentally deleted and if we try to
remove t
Public bug reported:
DVR router namespaces are deleted when we manually move the router from
on dvr_snat node to another dvr_snat node.
It should be only deleting the snat_namespace and not the
router_namespace, since there are 'dhcp' ports and 'vm' ports still
serviced by DVR.
How to reproduce:
Public bug reported:
L2 Gateway bridges the neutron network with the hardware based VxLAN
gateways. The DVR routers in neutron could not forward traffic to an
instance that is behind the VxLAN gateways since it could not 'ARP' for
those instances.
DVR currently has prepopulated ARP entries for al
Public bug reported:
The current 'link-lock-address allocator for DVR routers has a limit fo
256 routers per node.
This should be configurable and not just limit to 256 routers per node.
** Affects: neutron
Importance: Undecided
Status: Confirmed
** Tags: l3-dvr-backlog
** Chang
** Changed in: neutron
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1499045
Title:
get_snat_port_for_internal_port called twice when an interface
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1538369
Title:
re factor add_router_interface in l3_dvr_db.py
Status in neutron:
Op
Public bug reported:
DVR SNAT HA - Documentation for Networking guide for Mitaka.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutr
This is a known issue, since the router does not have an external
network interface in the router namespace and if you try to configure an
extra route pointing to the next hop which does not have a corresponding
interface in the router namespace.
This was a descision that we made since we don't wa
Public bug reported:
Recently we have seen the "Test_volume_backed_live_migration" fail with
Multinode gate setup.
This test failure is seen in nova/neutron etc.,
http://logs.openstack.org/17/258417/6/check/gate-tempest-dsvm-multinode-
full/0d516d3/console.html#_2016-02-24_17_43_48_123
** Affec
It was an invalid user configuration.
The "dvr"node was not configured with the right agent mode, and so this
issue was seen.
Please ignore this bug.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
DVR routers are not created on a compute node that is running L3 agent
in "dvr" mode.
This might have been introduced by the latest patch that changed the scheduling
behavior.
https://review.openstack.org/#/c/254837/
Steps to reproduce:
1. Stack up two nodes. ( dvr_snat no
Public bug reported:
In recent L3 agent logs in the gate we have been seeing this warning message
associated with the DVR router jobs.
Right now none of the jobs are failing, but we need to see why this warning
message is showing up in the logs or it might be due to some hidden issues.
http://
Public bug reported:
DVR arp update (dvr_vmarp_table_update) and dvr_update_router_add_vm
called for every update_port if the mac_address changes or when
update_devic_up is true.
These functions should be called from _notify_l3_agent_port_update, only
when a host binding for a service port change
Public bug reported:
Today "SSHTimeout" Errors are seen both in CVR ( Centralized Virtual Routers)
and DVR ( Distributed Virtual Routers).
The frequency of occurence is more on DVR than the CVR.
But the problem here, is the error statement that is returned and the data that
is dumped.
SSHTimeou
might be taking lot more time.
So we need to figure out the issue and reduce the time taken for the
scheduling.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
--
You received this bug
Not able to reproduce I could see the arp table update on the router
namespaces on both nodes.
I tried to modify the ports on both the subnet 10.2.0.X and 10.0.0.X.
In this example I have change the 10.2.0.4 to 10.2.0.25 and 10.0.0.8 10.0.0.20.
In both cases I saw that the arp entry was updated.
Public bug reported:
"test_dualnet_dhcp6_stateless_from_os" - This test fails in the gate
randomly both with DVR and non-DVR routers.
http://logs.openstack.org/79/230079/27/check/gate-tempest-dsvm-neutron-
full/1caed8b/logs/testr_results.html.gz
http://logs.openstack.org/85/238485/1/check/gate-t
Public bug reported:
I am seeing "gate-neutron-python34" test failures again in neutron.
http://logs.openstack.org/82/228582/13/check/gate-neutron-
python34/5b36c34/console.html
http://logs.openstack.org/82/228582/13/check/gate-neutron-
python34/5b36c34/console.html#_2015-10-07_17_36_06_987
**
te_dvr_fip_interfaces
/opt/stack/new/neutron/neutron/agent/l3/dvr_local_router.py:427
2015-09-29 21:10:34.043 DEBUG neutron.agent.l3.dvr_fip_ns
[req-33413b07-784c-469e-8a35-0e20312a157e None None] add
fip-namespace(fip-31689320-95d7-44f9-932a-cc82c1bca2b4) create
/opt/stack/new/neutron/neutron
22e4-5fef-4889-9372-8cf1218522a2 None None] adding internal network:
prefix(qr-), port(b672ffde-cd80-49eb-9817-58436fa8e8fd)
_internal_network_added
/opt/stack/new/neutron/neutron/agent/l3/router_info.py:300
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swami
Public bug reported:
In DVR routers static routes are now only added to snat namespace.
But before adding to snat namespace, the routers are not checked for the
existence of gateway.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: l3-dvr-backlog
--
You received t
Public bug reported:
Static routes are not added to the qrouter namespace when routers are
added.
Initially it used to be configuring the routes in the qrouter namespace but not
in the SNAT namespace.
A recent patch caused this regression in moving the routes from qrouter
namespace to SNAT name
' and again it is called by the
'dvr_edge_router.py'.
This can be reduced to a single call to improve the controll plane
performance.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
**
: (unassigned) => Swaminathan Vasudevan (swaminathan-vasudevan)
** Tags added: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1419175
Title:
Cannot find device "qr-" error
failure it seems when a gateway is removed, the
"get_snat_port_for_internal_port" is called without the cache value.
This bug was introduced by the patch shown below.
Icc099c1a97e3e68eeaf4690bc83167ba30d8099a
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Va
Public bug reported:
This bug would capture all the IPv6 related work on DVR routers going
forward.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: In Progress
** Tags: l3-dvr-backlog
--
You received this bug
uot; when trying to delete the
"floatingip_agent_gateway_port".
"Floatingip_agent_gateway_port" calls "_delete_port" and so the
"ML2PLugin" throws attribute not found error with recent changes.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan
*** This bug is a duplicate of bug 1404823 ***
https://bugs.launchpad.net/bugs/1404823
** This bug is no longer a duplicate of bug 1456756
Could not retrieve gateway port for subnet
** This bug has been marked a duplicate of bug 1404823
router-interface-add port succeed but does not add
Public bug reported:
FloatingIP Agent Gateway port is created on the nodes to substitute for the
Gateway port, since gateway port is currently residing on the Network Node.
So it makes sense for the server to delete the FloatingIP Agent Gateway Port
only when the External Gateway Port is deleted
Public bug reported:
DVR today has issues with supporting multiple subnets per network on its
routers.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: New
** Tags: l3-dvr-backlog
--
You received this bug
Let us go ahead and close this bug.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1426165
Title:
DVR: "Device or resource busy" err
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1398446
Title:
Nova compute failed to delete VM port with DVR
Status in OpenS
Public bug reported:
TRACE seen in the vpn-agent log when configured with DVR router.
A recent refactoring to the agent have introduced this problem.
http://logs.openstack.org/71/130471/6/check/check-tempest-dsvm-neutron-
dvr/10208dc/logs/screen-q-vpn.txt.gz?level=TRACE
2015-03-11 14:09:03.570
FloatingIP Agent Gateway Ports
for Legacy routers which are not utilized.
Only DVR routers require L3 agent to be present in the Compute Node.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan-vasudevan)
Status: New
** Tags: l3-dvr-backlog
Public bug reported:
FloatingIP Agent Gateway port should be deleted based on the host and
also based on the External network id.
In the Multiple external network scenario what happens is there might be
more than one FloatingIP Agent Gateway Port on the same host and so it
has to be deleted based
Public bug reported:
A recent change in the agent code have introduced this problem.
When a Gateway is cleared from the router, even though there are no existing
floating IPs, the "external_gateway_removed" function in "agent.py" is calling
"process_floatingips".
That may be the reason for thi
Public bug reported:
Remove unsued RPC methods from the L3_rpc.
The "get_snat_router_interface_ports" is defined but not currently used by any
agents. So it need to be cleaned.
** Affects: neutron
Importance: Undecided
Assignee: Swaminathan Vasudevan (swaminathan
Public bug reported:
This TRACE is seen in many places in the neutron l3-agent logs from the
jenkins logs.
2015-02-02 23:29:13.916 ERROR oslo_messaging.rpc.dispatcher
[req-ce57a6b0-04fc-41dd-a114-5b69c0ebcf6d FloatingIPsNegativeTestJSON-267704990
FloatingIPsNegativeTestJSON-594738290] Exception
1 - 100 of 120 matches
Mail list logo
