The openstack-neutron package has been rebased to the upstream stable release 2013.2.2. The fixes included in this release were backported from the development branches into a stable branch. This release is intended to be a low-risk update with no intentional regressions or API changes. Notable bug fixes applied by this rebase include: - The openstack-neutron service no longer prevents the addition of a security group rule that allowed all ingress IPv4/6. Previously, openstack-neutron's filter for querying existing rules used a wildcard incorrectly, resulting in a false match. - When a network cannot be found after it has been deleted, the resulting DHCP log traces are now Warnings instead of Exceptions. The severity of such warnings were reduced since the related agents can handle such situations as normal. - DHCP notifications are now sent regardless of agent status. This improves the DHCP stability during high loads. - When running 'neutron meter-label-delete', a router's tenant ID is no longer incorrectly deleted. - The neutron client now expects the correct token to be passed by the neutron-metadata-agent. This fix prevents the client from having to authenticate against the Identity service during each metadata request. Before this fix, simultaneously invoking multiple Compute instances with cloud-init resulted in high CPU virtualization by the Identity service. For a complete list of fixes applied by this rebase, refer to the following link: https://launchpad.net/neutron/havana/2013.2.2