Public bug reported:
Currently, one can set the ip_allocation attribute to "none" on a port
with the neutron API [1] or the python-neutronclient [2].
This is useful for instantiating a VM that doesn't have an IP, and
fixing [3]
However, to be able to read this attribute, the ip_allocation
Public bug reported:
Using latest neutron [1] and python-neutronclient [2], we are now able
to create VMs without IP addresses.
If I run :
$ openstack network create net1
$ openstack port create --network net1 port_net1
I get the IP_allocation field equal to "none" for the created port.
So
Public bug reported:
The change Ib6c2134d29e1764de627c3355f6cdee789d6301e in neutron cleans
up model query hooks registered after each tests is run. This cleanup
has been added in tests/base.py
In net-bgpvpn, some features rely on those hooks, and UTs for those
features are now broken, as we can
** Also affects: bgpvpn
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/1629133
Title:
New neutron subnet pool support breaks multinode
** Changed in: bgpvpn
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/1554452
Title:
Request release for networking-bgpvpn
Status in bgpvpn:
** No longer affects: bgpvpn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1512324
Title:
networking-bgpvpn kilo branch
Status in neutron:
Fix Released
Bug description:
While we
** Changed in: bgpvpn
Status: New => Won't Fix
** Changed in: neutron
Status: Confirmed => Fix Released
** Changed in: bgpvpn
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** Changed in: bgpvpn
Milestone: 4.0.0 => None
** No longer affects: neutron
** Changed in: bgpvpn
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
The following fullstack test environment, which setup 3 ovs agents with
vxlan networks, won't work :
class Test3Hosts(base.BaseFullStackTestCase):
def setUp(self):
host_descriptions = [
environment.HostDescription(l3_agent=False) for _ in range(3)]
Public bug reported:
Some external plugins might need to prevent the attachment of a subnet
to a router, like reported in bug [1]
Now that [2] has been fixed, we can prevent this attachment by adding a new
BEFORE_UPDATE callback in ML2, which will be triggered when the router port
gets updated
We can remove the bgpvpn project as an affected project. The related bug
in bgpvpn will be :
https://bugs.launchpad.net/bgpvpn/+bug/1537067
** No longer affects: bgpvpn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
split('=', 1)
ValueError: need more than 1 value to unpack
The root cause seems to be a bug in tox 2.3.0 :
https://bitbucket.org/hpk42/tox/issues/181
It works fine with tox 2.3.1.
Other openstack projects report similar errors :
https://bugs.launchpad.net/devstack/+bug/1525352
** Affects
** Changed in: nova
Status: Incomplete => Invalid
--
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/1441054
Title:
live-migration --block-migrate fails with default
Public bug reported:
Currently, no devref exists about interactions between nova and neutron when
nova performs a live-migration.
This would be useful to better understand how neutron can detect that a
live-migration is ongoing, and perform dedicated treatments if needed.
This could be a
Public bug reported:
The networking-bgpvpn project is now ready to have its first release.
We'd like to create a dedicated branch to backport needed patches in the
future.
Release Info :
Current branch : master
Commit-Id : 157f73d3f248f1e1008e1e7f908dd616762325bc
New Tag: 3.0.0
** Affects:
** 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/1492021
Title:
bagpipe: do not overload the ovs agent
Status in
** 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/1519258
Title:
agent not notified on update_device_down
Status in
Public bug reported:
The check of the tenant done in
neutron/db/common_db_mixin._get_tenant_id_for_create() is already did by the
Neutron Controller in prepare_request_body(), with a call to
attibutes.populate_tenant_id().
Moreover, when the Controller processes a "create" requests, it will add
Public bug reported:
When I run tests localy with ./run_tests.sh or tox -e py27, it
constantly fails in the oslo_policy package.
For instance :
$ ./run_tests.sh
neutron.tests.unit.extensions.test_securitygroup.TestSecurityGroups.test_create_security_group_rule_bad_tenant_security_group_rule
Public bug reported:
We propose to extend the neutron API to allow tenants to stretch their
BGP based IP VPN to their Openstack project.
This extension would allow to create BGPVPN connection objects based on
route targets informations. A BGPVPN objects would be assign to a
tenant. The tenant
Public bug reported:
in VPNaas, the command :
$ python -m subunit.run discover -t ./ ./neutron_vpnaas/tests/unit
--list | grep test_ikepolicy_list
doesn't return any result, while there is a test named
test_ikepolicy_list :
https://github.com/openstack/neutron-
Importance: Undecided
Assignee: Mathieu Rohon (mathieu-rohon)
Status: In Progress
--
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/1441054
Title:
live
Actually, once nova send port_update() message to notify the new host of the
port, ML2 will send update_port( to every agents.
The agent which is hosting the port will now resend
get_device_details()/update_device_up() and the port will not remain in BUILD
state.
That's the reason why I'm
Public bug reported:
I've set up a lab where live migration can occur in block mode
It seems that if I leave the default config, block live-migration fails;
I can see that the port is left in BUILD state after the failure, but
the VM is still running on the source host.
** Affects: neutron
thanks to dims, I understood that my devstack were too old.
The change Idecf7966968369d2f372abffcab85fbf9aa097c7 in devstack is
fixing this bug
https://github.com/openstack-
dev/devstack/commit/d2287cfb9f4dfac71f14f3374514f5b8c2b0c70b
** Changed in: nova
Status: Incomplete = Invalid
--
Public bug reported:
I'm using the libvirt driver
I've configured libvirtd and nova so that block migration can occur.
I boot a simple cirros, with no config drive; when I ask for a live-
migration I get this error on my source node, concerning the
incompatibily between live-migration and the
Public bug reported:
Currently, when one modify the IP of a port, a fdb message is sent even
if the port is not ACTIVE.
This could generate a racy behavior, since agents can receive a
fdb_update(chg_ip) message while they didn't yet received a fdb_add
message for this port. Indeed, fdb_add
Public bug reported:
This bug comes from a split of the bug #1365476 which will now be
dedicated to an OVS fix
There is big difference between OVS and LB when using vxlan tunnels
managed by l2pop :
-In OVS, vxlan tunnels are plugged into the br-tun bridge. L2pop
messages will manage the tunnel
this was a config issue, the local_ip was wrong in the vxlan section of
ml2_conf.ini, on the node 2
** 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.
neutron.plugins.ml2.plugin
[req-6ce7d002-8c96-45db-89b0-b6fa0681df73 None None] In _notify_port_updated(),
no bound segment for port ff1de9c4-4638-439b-9e52-b4bdb5c4cc8d on network
69e6c19e-8245-424c-a667-1531c55ee9d3
** Affects: neutron
Importance: Undecided
Assignee: Mathieu Rohon (mathieu
:
https://bugs.launchpad.net/neutron/+bug/1282662
we should use ip neigh replace instead of ip neigh add'
** Affects: neutron
Importance: Undecided
Assignee: Mathieu Rohon (mathieu-rohon)
Status: New
** Changed in: neutron
Assignee: (unassigned) = Mathieu Rohon (mathieu-rohon
Public bug reported:
ip_lib is now able to add neighboring entries. L2population should can
use this new feature once this patch will be merged :
https://review.openstack.org/#/c/89522/
** Affects: neutron
Importance: Undecided
Assignee: Mathieu Rohon (mathieu-rohon)
Status
Public bug reported:
currently, one can specify the vxlan udp port in the agent ml2_conf.ini
with :
[agent]
vxlan_udp_port = 8472
with this option, ovs will listen for vxlan packets on vxlan_udp_port and
will send vxlan packets on the same port, regardless which port the other vxlan
tunnel
Public bug reported:
When I deploy nova with a shared storage and with
neutron/ML2/linuxbridge, I have an error when I want to to use nova
evacuate
command :
# nova evacuate 1fa486f3-259c-4e1e-ae82-8b52606f1efd devstack2
--on-shared-storage
here are the logs on the compute node (devstack2)
aaron,
fdb entries are forwarding information on the bridge of the host, and the ip
neighbouring entries stands for the ARP responder entries.
I have one network node and two compute nodes
I first create a VM with IP 10.0.0.104 and MAC 00:00:00:44:44:44 on
node1, then on network node I have :
** Changed in: nova
Status: Incomplete = Invalid
--
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/1277582
Title:
live-migration : no error on CLI but an error in
Public bug reported:
I run in multi node setup with ML2, L2-population and Linuxbridge MD,
and vxlan TypeDriver.
I start two compute-nodes, I launch a VM, and I shutdown the compute-
node which host the VM.
I use this process to relaunch the VM on the other compute-node :
Public bug reported:
I run in multi node setup with ML2, L2-population and Linuxbridge MD,
and vxlan TypeDriver.
I create a VM with ip 10.0.0.105 and mac 00:00:00:55:55:55
neighbouring table on network node :
# ip neigh show
10.0.0.105 dev vxlan-1001 lladdr 00:00:00:55:55:55 PERMANENT
I delete
Public bug reported:
I run in multi node setup with ML2, L2-population and Linuxbridge MD, ad
vxlan TD.
I creat 2 VM on different node. When a port gets down on a node with :
neutron update_port port_uuid --admin_state_up False
Unicast fdb entries are correctly removed but from the node that
Public bug reported:
when I run :
#nova live-migration 90e9804e-4e93-446d-ade3-9143421ee5b9 devstack3
I get this :
ERROR: Unable to migrate instance (72939da1-1a41-4a2a-8bf4-1136008ffa26)
to current host (devstack3). (HTTP 400) (Request-ID: req-
3e9b5036-1072-4553-bac5-8f02d9659611)
but the
** Also affects: nova
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/1274160
Title:
port_update from nova could potentially occurs after
the agent could trigger its RPC message before
neutron receives its API call.
** Affects: neutron
Importance: Undecided
Assignee: Mathieu Rohon (mathieu-rohon)
Status: New
** Changed in: neutron
Assignee: (unassigned) = Mathieu Rohon (mathieu-rohon)
--
You received
42 matches
Mail list logo
