unable to create port with same ip with dhcp_enabled=false

[Aaron Rosen]

If you create a network and subnet that is set to dhcp_enabled=False. If you then create a port specifying the ip address and then delete it; you will not be able to recreate the port with the same ip address until the dhcp lease time has passed even though dhcp is disabled. This will be fixed by the blueprint remove-dhcp-lease but created bug report for issue tracking.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/37580

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/37580
Committed: http://github.com/openstack/neutron/commit/d9832282cf656b162c51afdefb830dacab72defe
Submitter: Jenkins
Branch: master

commit d9832282cf656b162c51afdefb830dacab72defe
Author: Aaron Rosen <email address hidden>
Date: Tue Jul 16 16:06:32 2013 -0700

    Remove DHCP lease logic

    Previously neutron was keeping track of dhcp lease time in order
    to ensure it didn't hand out an ip address that was already leased.
    This patch removes that logic and instead leverages the dhcp_release
    utility. This allows us to reuse ip addresses immediately after a port
    is deleted. This patch also bumps the lease time to 24 hours instead
    of 2 minutes with reduces the amount of dhcp traffic.

    DocImpact

    There is a DocImpact for this bug related to the upgrade path. One should
    first upgrade their dhcp-agents. Then wait till the dhcp_lease time has
    expired. Lastly, update neutron-server in order to avoid the case where
    an instance is deleted and the dnsmasq process has not released the lease
    and neturon allocates that ip to a new port.

    Fixes bug: 1202392
    Implements blueprint: remove-dhcp-lease

    Change-Id: Ifcb4f093c92904ceb896438987d53e692eb7fb26