Public bug reported:
The following code is from
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent.treat_devices_added_or_updated():
devices_details_list = (
self.plugin_rpc.get_devices_details_list_and_failed_devices(
self.context,
Public bug reported:
There's a race condition between the time compute deletes a neutron port
during destroy instance processing and the time the ovs_neutron_agent
rpc_loop notices the ovs port removed and tries to update the associated
neutron port to set the state to DOWN.
In our scenario, cont
Public bug reported:
In setting the nova_api_insecure flag to True in neutron.conf, I've
found that neutron/notifiers/nova.py does not honor this flag. In fact,
it does not even pass any insecure parm at all on the invocation of
Client().
https://github.com/openstack/neutron/blob/master/neutron/
It's been decided to abandon this fix because it's preventing something
that, while not useful, is technically "ok". The better place for this
fix would be in the UI as a hint to the user.
For more info: http://lists.openstack.org/pipermail/openstack-
dev/2014-January/025385.html
** Changed in:
stack/neutron/blob/master/neutron/plugins/ml2/managers.py.
It would be nice if the MechanismDriverError at least contained the
exception details from the last exception encountered in the driver
chain.
** Affects: neutron
Importance: Undecided
Assignee: Paul Ward (wpward)
Status
y the gateway,
thus making this network a dead network since no IPs are left over to be
allocated to VMs.
I propose a change to disallow start_ip == end_ip in
NeutronDbPluginV2._validate_allocation_pools() to cover the CIDR of /32
case.
** Affects: neutron
Importance: Undecided
Assignee: Paul
r. If the
segmentation_id is out of the range, then raise an InvalidInput
exception as is already done for other violations.
** Affects: neutron
Importance: Undecided
Assignee: Paul Ward (wpward)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Paul Ward (wpw
7 matches
Mail list logo
