Since all the changes seemed to have merge will close this.
** Changed in: neutron
Status: New => 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/1862315
Title:
Somet
Public bug reported:
I noticed while looking at a horizon backport,
https://review.opendev.org/c/openstack/horizon/+/866891
that the test_volumes_pagination job was failing in both the stable and master
branches.
It's usually a "'NoneType' object is not iterable" failure, here's an
example:
htt
Fixed in https://review.opendev.org/c/openstack/horizon/+/847985 will
close this bug.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs
** 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/2012144
Title:
[OVN] adding/removing floating IPs neutron server errors about b
** Changed in: neutron
Status: In Progress => 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/2009053
Title:
OVN: default stateless SG blocks metadata traffic
Status in
d an error since there was a subnet here,
will have to re-check the API ref to see.
During one attempt I actually triggered a SubnetNotFound error, but
that's probably a different issue as it wasn't necessary to recreate
this.
** Affects: neutron
Importance: Medium
Assignee
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => Brian Haley (brian-haley)
** Changed in: neutron
Importance: Undecided => Medium
** Tags added: ovn
--
You received this bug notification because you are a mem
Was just going through old bugs and patches and noticed this one,
updating based on information I received.
>From Salvatore:
"My recollection is the same as Akihiro. A tenant has no knowledge of IP
addressing beyond the resource it owns, and since a no-snat
configuration implies E-W L3 forwarding
*** This bug is a duplicate of bug 1830679 ***
https://bugs.launchpad.net/bugs/1830679
This was fixed in https://review.opendev.org/#/c/665566/ and backported
to stable/stein (15.0.0), it wasn't backported further.
Closing as a duplicate of
https://bugs.launchpad.net/neutron/+bug/1830679
**
This doesn't look like a bug in networking-ovn, but instead with nova, I
added them as an affected project.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: networking-ovn
Status: New => Incomplete
--
You received this bug notification because you are a me
** Project changed: networking-ovn => neutron
** Changed in: neutron
Importance: Undecided => Medium
** Tags added: ovn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1860273
Title:
r `encap:X,Y` if Y is numerical, or `encap:X,option:Y` if Y is text.
** Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
nges in that as well, https://review.opendev.org/#/c/703685/
** Affects: neutron
Importance: High
Assignee: Brian Haley (brian-haley)
Status: Confirmed
** Tags: ovn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscr
** 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/1753434
Title:
Unbound ports floating ip not working with address scopes in
I am going to close this bug, partly because it is so old without any
updates, but also because there have been a number of improvements over
the past few cycles wrt scaling that this is probably not as much an
issue any more.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You r
** 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/1789434
Title:
neutron_tempest_plugin.scenario.test_migration.NetworkMi
** Changed in: neutron
Status: In Progress => 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/1835731
Title:
Neutron server error: failed to update port DOWN
Status i
** 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/1595043
Title:
Make DVR portbinding implementation useful for HA ports
** 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/1766701
Title:
Trunk Tests are failing often in dvr-multinode scenario
** 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/1845557
Title:
DVR: FWaaS rules created for a router after the FIP and VM c
** 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/1717302
Title:
Tempest floatingip scenario tests failing on DVR Multino
** Changed in: neutron
Status: Incomplete => 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/1252900
Title:
Directional network performance issues with Neutron + OpenvSwi
Since there is a workaround, and this is only regarding the Linux Bridge
agent, which is not actively maintained, I'm closing this since it
doesn't seem like it will be fixed.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a mem
** Project changed: neutron => networking-bgp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1828547
Title:
neutron-dynamic-routing TypeError: argument of type 'NoneType' is not
iterab
** 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/1574092
Title:
No router namespace after creating legacy router
Status in neu
Closing as I don't think this happens any more.
** 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/1510757
Title:
tempest test api
** Changed in: neutron
Status: In Progress => 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/1668410
Title:
[SRU] Infinite loop trying to delete deleted HA router
St
There have been a number of issues fixed in this area the past few
releases, closing. If it still happens on a newer release please re-
open.
** Changed in: neutron
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** 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/1680183
Title:
neutron-keepalived-state-change fails with "AssertionError:
** Changed in: neutron
Status: New => 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/1666959
Title:
ha_vrrp_auth_type defaults to PASS which is insecure
Status in neutr
** Changed in: neutron
Status: In Progress => 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/1636466
Title:
HA router interface points to wrong host after network disrup
I think we've addressed all of the issues with the sysctl knobs in HA
routers over the past few cycles as part of other bugs, so I'll close
this bug.
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Te
it chose could still be in the middle of a
full sync.
** Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: New
** Tags: l3-ipam-dhcp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
ompletely breaking the gate but think it's an
easy fix.
** Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: New
** Tags: l3-ipam-dhcp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
** 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/1869862
Title:
neutron-tempest-plugin-designate-scenario failes frequently with
imag
** 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/1869768
Title:
devstack failed when Q_AGENT=ovn
Status in neutron:
Invalid
Using wsgi is not supported until Rocky,
https://review.opendev.org/#/c/555608/
The doc link you cite is for "latest" and doesn't exist under
https://docs.openstack.org/neutron/queens/admin/index.html
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification bec
Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: In Progress
** Tags: lib
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1882588
Tit
Public bug reported:
There are doc files in the neutron tree, for example, doc/source/admin
/config-dns-int-ext-serv.rst, that still show the "old" neutron client
commands instead of the new openstack client commands. They should all
be cleaned-up appropriately.
** Affects: neutron
Importan
** Project changed: neutron => nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1758112
Title:
Unable to launch Centos/CirrOS instance
Status in OpenStack Compute (n
*** This bug is a duplicate of bug 1745468 ***
https://bugs.launchpad.net/bugs/1745468
We actually just fixed the conntrack issue in master and it's being
backported to stable/queens. I'll link that bug and close this as a
duplicate.
** This bug has been marked a duplicate of bug 1745468
The "old" neutronclient shows the correct failure message:
$ neutron floatingip-associate 5d0dc3fa-fb22-42ad-b4c0-b539d47c6d4f
40cb7567-8860-45db-8e40-fca62dc9bad2
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
External network 62de8874-0e12-466a-8e21-2f9
*** This bug is a duplicate of bug 1750777 ***
https://bugs.launchpad.net/bugs/1750777
Thanks for the response.
Yeah, I probably should have tied those two changes closer together,
they unfortunately merged almost a week apart and the repo is probably
pulled nightly.
I'm not sure of the quic
** 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/1762376
Title:
openstack router create - multiple routers with same name in same
pro
** 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/1403455
Title:
neutron-netns-cleanup doesn't clean up all L3 agent spaw
e issue.
** Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: Confirmed
** Tags: l3-ipam-dhcp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net
n is _remove_conntrack_jump(), which is being called
when we're removing a set of chains./lin
** Affects: neutron
Importance: Undecided
Assignee: Brian Haley (brian-haley)
Status: New
** Tags: sg-fw
--
You received this bug notification because you are a member of Yahoo
This was already fixed on the master branch, commit
e1761d2e29cdd93dffe3d39c0b9407b2facaa0c1
** 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/
This was already fixed on the master branch, commit
e1761d2e29cdd93dffe3d39c0b9407b2facaa0c1
** 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/
I think this is now the third bug for this same issue, and it's already
been fixed in that file and is in progress on others, see commit commit
e1761d2e29cdd93dffe3d39c0b9407b2facaa0c1. So I don't think there is any
work to do.
** Changed in: neutron
Status: New => Incomplete
** Changed i
Already fixed.
** 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/1773585
Title:
Configuration auth_url Openstack Queens is wrong
Statu
Re-opened since bug 1774019 seems to be a duplicate. In that case a
user was able to add a router to a shared external network and it got
the .1 address. Looks like there is an edge case here we need to cover.
** Changed in: neutron
Status: Expired => Confirmed
** Changed in: neutron
This bug was already fixed on the master branch by
https://review.openstack.org/#/c/566491/ so please just cherry-pick that
to stable/queens. I'm closing this bug as it's one of many duplicates.
** Changed in: neutron
Status: Confirmed => Invalid
--
You received this bug notification bec
Yes, this is a known issue with certain kernel versions having broken
netfilter code. I don't have the exact upstream bug as reference, just
have a memory of seeing it tracked down.
So I will close as not a bug.
** Changed in: neutron
Status: New => Invalid
--
You received this bug noti
Please actually look at the source tree before filing bugs, this issue
was already fixed and yet this is the third or fourth bug filed for it.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Please look at the source url that you linked before filing bugs as this
has already been fixed.
** 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.
This has already been fixed.
** 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/1776587
Title:
Configure neutron services on compute and
This has already been fixed in the neutron master branch,
https://review.openstack.org/#/c/566491/
** 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.launchpa
This is already fixed in the neutron master branch,
https://review.openstack.org/#/c/566491/
** 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/
Already fixed in master branch.
** 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/118
Title:
Documentation Error for Queens Install
Already fixed in master branch.
** 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/1777977
Title:
Install and configure controller node
This has already been fixed in the master and backport is in
stable/queens review.
** 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/17820
affic should be going via the centralized router, but would like to
confirm with others.
** Affects: neutron
Importance: Undecided
Assignee: Brian Haley (brian-haley)
Status: New
** Tags: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
E
bject is returned. I'll
investigate changing the code.
** Affects: neutron
Importance: Medium
Assignee: Brian Haley (brian-haley)
Status: Confirmed
** Tags: tempest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
as intended for the owner originally with
the caveat that the admin could restrict if necessary.
This fix would be as simple as updating these two entries:
"create_router:external_gateway_info:enable_snat": "rule:admin_only"
"update_router:external_gateway_info:enable_snat":
*** This bug is a duplicate of bug 1757482 ***
https://bugs.launchpad.net/bugs/1757482
This looks like a duplicate of
https://bugs.launchpad.net/neutron/+bug/1757482 as I was unable to
reproduce it on master - trying to add the interface to the router got:
Error: Failed to add interface: Bad
e returning an error at all,
since an asynchronous event could have deleted the namespace, and since
it's no longer there we are in the desired state.
This will help with some of the recent issues we've had getting code
merged.
** Affects: neutron
Importance: High
Assignee: Bri
;flags': 0, 'encap': {}, 'src_len': 0, 'table': 254, 'multipath':
({'oif': 2, 'family': 10}, {'oif': 6, 'dst_len': 64, 'family': 10,
'proto': 2, 'tos': 0, 'pref': '00&#
** Project changed: neutron => bgpvpn
** Project changed: bgpvpn => networking-bgp
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1799455
Title:
AttributeError: 'BgpDrAgentNotifyApi' ob
Had to move this back from neutron to flip the status bit.
** Project changed: python-openstackclient => neutron
** 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:
This looks like a Keystone issue and not neutron, even though the
example command was against the neutron API.
** Project changed: neutron => keystone
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
Public bug reported:
In the context of a live datacenter, sometimes the network teams re-
organize their VLANs by changing VLAN IDs. This is pretty
straightforward in the context of network configuration and physical
servers, but when using ML2 VLAN provider networks, those IDs cannot be
updated.
Public bug reported:
Seeing this traceback in the l3-agent logs in the failing neutron-
tempest-plugin-dvr-multinode-scenario job.
For example,
http://logs.openstack.org/23/622623/3/check/neutron-tempest-plugin-dvr-multinode-scenario/604b3c0/controller/logs/screen-q-l3.txt.gz?level=WARNING
neutr
Public bug reported:
After fixing a bug in the L3 extension API,
https://review.openstack.org/#/c/626401/ - the l3-agent is getting a
traceback in the QoS code running the dvr multinode scenario job.
neutron-l3-agent[14973]: ERROR neutron.agent.l3.agent [-] Failed to process
compatible router: 7
** 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/1811941
Title:
neutron routers are down
Status in neutron:
Invalid
Bug desc
I've added the os-vif component based on Sean's comment.
** Also affects: os-vif
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/1815989
Title:
Public bug reported:
Recently saw this error in the dvr-multinode grenade job:
ERROR neutron.api.v2.resource [None req-efa49ab7-5bc4-49a4-9ede-e6f638f80004
admin admin] remove_router_interface failed: No details.: StaleDataError:
DELETE statement on table 'standardattributes' expected to delete
This is happening because by default, devstack enables the linuxbridge
mechanism driver when DVR mode != legacy, even though the linuxbridge
agent doesn't work with DVR.
Devstack needs to change to not enable the driver in this case.
** Affects: neutron
Importance: Low
Assignee: B
So this is a bug in openstacksdk and/or python-openstackclient code, by
default it is showing both "distributed" and "ha" values (with defaults
to False), even if they are not in the JSON body returned from neutron-
server. I don't know of an easy way to fix that by specifying not to
show it in th
Assignee: Brian Haley (brian-haley)
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/1717597
Title:
Bad arping call in DVR centralized
Don't know why the Closes-bug in the commit message didn't trigger an
update here, but this merged to master:
https://review.openstack.org/#/c/501852/
And this is proposed to Pike:
https://review.openstack.org/#/c/504515/
** Changed in: neutron
Status: Fix Released => In Progress
--
Yo
status,
which is the default state on the server side before sending the
message. Since the agent didn't respond it stays in that state
indefinitely.
I think when the OVS agent skips processing a port, it should notify the
server that it should be updated to the DOWN state, since it is not
cur
Actually, after asking for a review of the patch, I've abandoned it
since this behavior of allowing the gateway_ip valued not in the subnet
is intentional:
https://bugs.launchpad.net/neutron/+bug/1335023
So there are use cases where it is required, and being more strict would
break them.
** Chan
ubuntu, Password: None
We need to track these down so we can get this job passing.
** Affects: neutron
Importance: High
Assignee: Brian Haley (brian-haley)
Status: Confirmed
** Tags: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
En
#x27;network_id'] == network_id
>>> any(port_belongs(p) for p in foo)
Traceback (most recent call last):
File "", line 1, in
File "", line 1, in
File "", line 1, in
TypeError: 'NoneType' object has no attribute '__getitem__'
We n
I'm going to move this to Fix Released as the two changes Swami
mentioned were in Pike. If it's still a problem after upgrading to
that, or on master, please re-open.
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a memb
Using the openstackclient you should get a 403 error:
$ openstack floating ip create --floating-ip-address 172.24.4.99 public
Error while executing command: Forbidden (HTTP 403) (Request-ID:
req-1167e309-1975-4aa5-b3ae-7930723e0755)
This is an admin-only operation as per the default entry in
etc
I'm going to change the component to neutron-lbaas since this doesn't
seem to be caused by code in neutron proper. Looking at the lbaas code
quickly, it looks like this file:
drivers/haproxy/namespace_driver.py
Needs changes similar to what was done in:
https://review.openstack.org/#/c/4
t called after we verify an
ha_port exists in HaRouter.initialize().
Adding 'self.process_monitor = None' in RouterInfo.__init__ should fix
the problem.
** Affects: neutron
Importance: Undecided
Assignee: Brian Haley (brian-haley)
Status: In Progress
** Tags: l3-h
** Project changed: neutron => python-openstackclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1716789
Title:
Security Group empty protocol defaults to TCP
Status in python-openst
** Project changed: neutron => octavia
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1741123
Title:
neutron-lbaas endless haproxy restarts due to faulty Neutron port
fixed_ip field
S
fects: neutron
Importance: Low
Assignee: Brian Haley (brian-haley)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1742355
Title:
Don't try to c
IPs it might reduce the time it takes for cleanup.
** Affects: neutron
Importance: High
Assignee: Brian Haley (brian-haley)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bug
I don't see this in logstash any more, unless it's broken. I'll close
but please re-open if seen again.
** 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://b
| df427083b46c400e956f66ba952b3b55
|
| updated_at| 2016-10-05T20:59:56Z
|
+---+-----------+
**
Doh, I'm an idiot, john-davidge pointed out I forgot to add the router
interface to this subnet, I should know better :)
** 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.
Those methods had been marked for deprecation and were finally removed,
the NSX plugin needs to be updated to use the neutron-lib code instead.
** Project changed: neutron => vmware-nsx
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** 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/1611237
Title:
Restart neutron-openvswitch-agent get ERROR "Switch connection
** 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/1640555
Title:
In an environment with DVR, a VM with floating IP is not reachab
sage is getting printed. As the number
of ports and rules grow, it's spending more time spinning through chains
and rules. It looks like that can be helped with a small code change,
which is just fallout from the real problem. I'll send that out since
it helps a little.
More work st
301 - 400 of 516 matches
Mail list logo
