sk the OpenStack infra team
(#openstack-infra on freenode) for help if you need to.
commit f494de47fcef7776f7d29d5ceb2cc4db96bd1efd
Author: Carl Baldwin <carl.bald...@hpe.com>
Date: Tue Feb 9 16:39:01 2016 -0700
Associate subnets to segments through subnet API
** 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/1564776
Title:
DVR l3 agent should check for snat namespace existence before
://bugs.launchpad.net/neutron/+bug/1622616/
[2] https://review.openstack.org/#/c/369051/
[3] https://bugs.launchpad.net/neutron/+bug/1623800
** Affects: neutron
Importance: High
Assignee: Carl Baldwin (carl-baldwin)
Status: Confirmed
** Tags: l3-ipam-dhcp
--
You received this bug
: Low
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
** Changed in: neutron
Milestone: None => newton-rc1
** Changed in: neutron
Assignee: (unassigned) => Carl Baldwin (carl-baldwin)
** Changed in: neutron
Importance: Undecided => Low
--
You received
Public bug reported:
In looking through the retry mechanism for pluggable IPAM (e.g. [1]), I
found it is not robust. It catches only a very narrow set of errors.
Many other errors would not result in a rollback notification to the
external IPAM system. Basically, if anything else fails during a
Public bug reported:
This code [1] ends up emitting an "IndexError: list index out of range"
exception that ends up with a trace like this [2]. Essentially, there
are no fixed ips on the port. Not sure yet how it got in to this state.
This failure is linked to various tempest failures in
Public bug reported:
This bug is visible when pluggable IPAM is active. It can be seen with
this patch [1]. It does not cause gate failures but it is still
something that should be understood. This logstash query [2] seems to
find where they occur. It is helpful to look at the DEBUG level
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Status: New => In Progress
** Changed in: neutron
Importance: Undecided => Wishlist
** Tags removed: rfe
** Tags added: rfe-approved
--
You received this bug notification because you are a
Public bug reported:
At the end of deleting a GW port for a router, l3_dvr_db.py will look
for any more router gw ports on the external network. If there are
none, then it calls delete_floatingip_agent_gateway_port [1]. This
should fan out to all l3 agents on all compute nodes [2]. Each agent
We never really provided an official migration. Some vendors like
InfoBlox have an unofficial one in order to facilitate migrating to
their drivers. The reason for this is that the internal driver doesn't
provide any advantage over the non-pluggable implementation. It is
effectively equivalent.
** Changed in: neutron
Status: Fix Released => In Progress
** Description changed:
+ Llatest patch (2016-06-10): https://review.openstack.org/#/c/326729/
+
Stale snat namespace on the controller after recovery of dead l3 agent.
Note: Only on Stable/LIBERTY Branch:
-
Setup:
** Changed in: neutron
Status: Triaged => 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/1566191
Title:
[RFE] Allow multiple networks with FIP range to be associated
Update from Drivers' meeting:
http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-06-02-22.00.log.html#l-124
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
This was filed from a null-merge. I think it is okay to mark it
invalid.
** 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/1586135
Public bug reported:
I found this yesterday while working on deferred IP allocation for
routed networks. However, it isn't unique to deferred port binding.
With my deferred IP allocation patch [2], I need to be able to make a
port create call [1] without binding information that doesn't allocate
Public bug reported:
Several people now, including Brian Haley and me, have been chasing down
this stack trace [1] for a few weeks. We've seen it in failed jobs and
we begin chasing it down only to find out that it is a red herring.
I'm filing this bug because we ought to capture what we know
This is no longer relevant. The default subnetpool behavior has changed
in Mitaka. You need to request the use of a default subnetpool
explicitly. That makes this problem moot.
** Changed in: neutron
Status: Confirmed => Invalid
** Changed in: openstack-manuals
Status: Confirmed
I think we should do just enough of this for the fast exit rfe [1] and
leave the rest of this for another time.
[1] https://bugs.launchpad.net/neutron/+bug/1577488
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of
After talking with Sukhdev and a Manila person at the summit on Friday
and looking at the Manila use case, I understand much better what the
use case is you're after here. An ML2 mechanism driver that will bind
the port to the Manila file server will have access to all of the
details it needs.
In my review of the patch, I stated that I think the cure is much worse
than the problem. I don't think anyone has chimed in to change my mind
and so I'm marking this as won't fix. Ping me if you think it should be
fixed.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You
** 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/1536437
Title:
'module' object has no attribute 'moved_function'
/db/ipam_non_pluggable_backend.py#L248-249
[2]
https://github.com/openstack/neutron/blob/c5bc5bda34/neutron/ipam/utils.py#L28
[3]
https://github.com/openstack/neutron/blob/c5bc5bda34/neutron/db/ipam_non_pluggable_backend.py#L268
** Affects: neutron
Importance: Low
Assignee: Carl Baldwin
I pushed the tag to gerrit. Please confirm that the release was
successful.
** 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.
After some review and reading Neil's final comments, I'm going to close
this. I'm about to crack IPAM for routed networks. With this request
in mind, I'll be looking to evolve the IPAM interface so that it can
take host information into consideration. I'll also be working on the
deferred IP
We won't support this on the API. But, I don't think we'd need to
anyway. Let me explain...
In the Neutron model, routers attach to subnets, a part of the network.
If you show the network, it lists the subnets that belong to it:
$ neutron net-show private
It needs them all! DVR routing is supposed to be able to do east/west
routing locally on the compute host. If the router is connected to 10
subnets, it needs to have 10 interfaces in order for traffic to egress
on any one of them.
Did I miss something?
** Changed in: neutron
Status: In
neutron: https://review.openstack.org/#/c/282021/
python-neutronclient: https://review.openstack.org/#/c/282583/
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Assignee: (unassigned) => Carl Baldwin (carl-bald
discussing [1], I agreed to provide a new extension to make this
convenient again. The extension should be added to the server side to
allow any API consumers to make use of it.
[1] https://bugs.launchpad.net/neutron/+bug/1545199
** Affects: neutron
Importance: High
Assignee: Carl Baldwin
Public bug reported:
I've been thinking about this for a little while now. There seems to be
something different about floating IP subnets and other (I'll call them
static in this context) subnets in some use cases.
- On an external network where operators wish to use private IPs for router
Public bug reported:
This is a known limitation in the reference implementation of address
scopes [1] in the L3 agent that a router cannot be connected to subnets
with overlapping IPs even when the subnets are in different address
scopes and, in theory, there should be no ambiguity. This was
** Changed in: neutron
Status: Won't Fix => 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/1370033
Title:
Admin should be able to manually select the active instance of a HA
I just adjusted the status and tags to reflect what has been discussed
on the review [1]. Maybe we need to discuss this again in the drivers
team meeting.
[1] https://review.openstack.org/#/c/257299/
** Tags removed: rfe-approved
** Tags added: rfe
** Changed in: neutron
Status: In
** 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/1531375
Title:
useless slash in the return message when create a subnet with
Interesting. So, having multiple threads doesn't improve the execution
time at all? That's different than I remember.
One thing that have some number of threads may do is possibly decrease
the latency to process a new request while some threads are working on
other routers.
** Changed in:
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1527129
Title:
The allocation_pools attribute of the subnet only affects the automatic
allocation of IPs for new ports created after the pool is set. It is
not intended to affect existing or manually created ports.
** Tags added: l3-ipam-dhcp
** Changed in: neutron
Status: New => Won't Fix
--
You
Reopen if this is shown to be more severe than we currently think it is.
** 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.
** 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/1189658
Title:
Should choice of DHCP gateway consider whether a subnet's gateway is
This extension is a shim extension. It indicates the presence of the
feature but doesn't actually provide the feature. The reason it is
there is due to some confusion about the future of extensions at the
time of development. It was developed as a core resource but then at
the very last hour
At this point, given that fwaas is totally up in the air, I don't think
we're going to take on anymore DVR / FWaaS bugs.
** 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
** 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/1411883
Title:
DVR qrouters are not created when VMs are added after the
** 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/1479887
Title:
Default subnetpools cannot be defined by name
Status in
** Changed in: neutron
Status: Confirmed = Incomplete
** 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/1383571
Title:
** 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/1034161
Title:
some platforms do not support namespaces
Status in neutron:
** Changed in: neutron
Importance: Undecided = Medium
** 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/1428305
Title:
Public bug reported:
It looks like _validate_subnet is not called when allocating from a
subnet pool. See here [1] for a discussion about it.
[1]
https://review.openstack.org/#/c/153236/89/neutron/db/db_base_plugin_v2.py
** Affects: neutron
Importance: Undecided
Assignee: Ryan
I just added python-neutronclient to this bug report. The fact that the
client defaults to IP version 4 even when a version 6 subnet pool has
been selected should be fixed.
** Also affects: python-neutronclient
Importance: Undecided
Status: New
--
You received this bug notification
I marked this invalid because it is not required for existing specs
until Liberty-1 and I won't update it to follow the new guidelines until
that is necessary. Please ignore this and use the blueprint for up-to-
date information.
** Changed in: neutron
Status: New = Invalid
--
You
Gotta get this one out of here too, I guess.
** 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/1453906
Title:
Implement Routing
I'm sorry to offend you with 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/1453921
Title:
Implement Address Scopes
Status in
Public bug reported:
See the spec for more details https://review.openstack.org/#/c/88623
This dns_label field will be used for DNS resolution of the hostname in
dnsmasq and also will be used when Neutron can integrate with external
DNS systems.
** Affects: neutron
Importance: Undecided
Public bug reported:
We propose create an new dr-agent which speaks BGP on behalf of Neutron
to external routers. It will only announce routes on an external
network and will not yet learn routers from the external system.
These routes will include floating IPs in IPv4 and IPv6 subnets for
Public bug reported:
This feature request proposes to allow using private subnets and public
subnets together on the same physical network. The private network will
be used for router next-hops and other router communication.
This will also allow having an L3 only routed network which spans L2
Public bug reported:
Make address scopes a first class thing in Neutron and make Neutron
routers aware of them.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
The reason for not allowing the gateway to be within the allocation
pools was so that Neutron would not allocate the gateway IP address to
just anything. It should be specifically requested for a router port or
a service VM like you've done.
If we allow moving the gateway IP to an IP inside the
Public bug reported:
The following command ends up creating a subnet with ip_version set to 4
even though the pool is an ipv6 pool.
$ neutron subnet-create --subnetpool ext-subnet-pool --prefixlen 64
network1
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl
** Changed in: neutron
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1287824
Title:
l3 agent makes too many individual sudo/ip netns calls
Public bug reported:
I'm getting a pylint error on my newest patch [2] that doesn't seem to
be related to the patch. I seem to get the same error on master.
Logstash is hinting at something starting to go wrong [1].
Possible unbalanced tuple unpacking with sequence defined at line 153:
left
can be called. If it is important to
disable_ipv6_ra for router namespaces then this call should be moved to
_destroy_router_namespace.
** Affects: neutron
Importance: Medium
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
** Changed in: neutron
Importance
: Carl Baldwin (carl-baldwin)
Status: Confirmed
** Tags: l3-dvr-backlog
** Changed in: neutron
Importance: Undecided = Medium
** Tags added: l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) = Carl Baldwin (carl-baldwin)
** Changed in: neutron
Status: New
is necessary because there is only one thread active and the
method waits for it to complete at the end.
3. The set logic is no longer needed.
** Affects: neutron
Importance: Wishlist
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
--
You received this bug
It seems this has been fixed with
https://review.openstack.org/#/c/37580/
** 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.
** 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/1156980
Title:
Agent is not a L3 Agent or has been disabled
Status in
** 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/1224502
Title:
Getting No more IP addresses available error , though enough
Closing at Robert's request. Sorry it took so long.
** 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/1184519
Title:
after
Public bug reported:
We've hit this foreign key constraint error. This is due to a sync
message coming in from the L3 agent over RPC. The message contains n
update for a port that has just been deleted. This is just log noise
because it all gets worked out quickly following the error. The
for the DVR router.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
** Tags: l3-dvr-backlog
** Tags added: l3-dvr-backlog
** Changed in: neutron
Assignee: (unassigned) = Carl Baldwin (carl-baldwin)
--
You received this bug
Public bug reported:
This was a know backlog item when DVR code merged.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: l3-dvr-backlog
** Tags added: l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
*** This bug is a duplicate of bug 1315467 ***
https://bugs.launchpad.net/bugs/1315467
** This bug is no longer a duplicate of bug 1325800
Potential Race Condition between L3NATAgent.routers_updated and
L3NATAgent._rpc_loop.
** This bug has been marked a duplicate of bug 1315467
*** This bug is a duplicate of bug 1315467 ***
https://bugs.launchpad.net/bugs/1315467
After looking at the code, I'm confident that the eventlet threading
model does not allow this race condition in the most current code. Here
are the lines of code in question in the current master branch:
Public bug reported:
I was testing https://review.openstack.org/#/c/62042 and found that the
python neutron client is unable to update fields in a subnet, especially
the allocation pools.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: neutron
Assignee: (unassigned) = Carl Baldwin (carl-baldwin)
** Project changed: neutron = python-neutronclient
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1324189
Public bug reported:
Just came across this. I noticed that the ip_lib.py code uses replace
instead of add. Using the common code would be good anyway.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
This subject came up on IRC here [1]. It relates to the blueprint about
pluggable external network connections and so I jumped in.
There are two reasons that using multiple external networks to allow multiple
floating ip subnets [2] is not optimal.
- Extra L2 infrastructure
Assignee: Carl Baldwin (carl-baldwin)
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/1301035
Title:
Nova notifier thread does not run in rpc_worker sub-processes
comes back up, it will
not touch the router and the router will continue to function as if it
were never deleted.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
--
You received this bug notification because you are a member
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
Status: New
** Changed in: neutron
Assignee: (unassigned) = Carl Baldwin (carl-baldwin)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https
precedence over responding to RPC messages. The RPC
messages represent work that the system has just been asked to perform.
It is silly to make it wait a long time for a maintenance task to
complete.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin
does not
itself add a lot of overhead.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https
)
ip_wrapper.netns.execute(cmd)
else:
utils.execute(cmd, self.root_helper)
This code could be simplified if netns.execute simply checked if there
was a namespace defined or not.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
Status: In Progress
Public bug reported:
I'm running wait in ProcessLauncher in a green thread. I attempted to
kill the green thread and then call wait so that the process launcher
object can reap its child processes cleanly. This resulted in a trace
resulting from a GreenletExit exception being thrown.
The
Public bug reported:
I noticed this while reviewing Ic2c87174. When I read through log
files, I don't want to see errors like this that come from validating
bad user input. Debug severity is more appropriate.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl
.
** Affects: neutron
Importance: Undecided
Assignee: Carl Baldwin (carl-baldwin)
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/1263217
Title
83 matches
Mail list logo
