Hi, Once [1] merges, a port will not transition to ACTIVE on a subnet with enable_dhcp=True unless something clears the DHCP provisioning block. If your mechanism driver uses the in-tree DHCP agent, there is nothing you need to do. However, if you do not utilize the DHCP agent in your deployment scenarios and you offload DHCP to something else, your mechanism driver must now explicitly acknowledge that DHCP has been provisioned for that port. Acknowledging that DHCP is ready for a port is a one-line call to the provisioning_blocks module[2]. For more information on provisioning blocks, see [3]. 1. https://review.openstack.org/452009 2. https://github.com/openstack/neutron/blob/4ed53a880714fd33280064c58e6f91 b9ecd3823e/neutron/api/rpc/handlers/dhcp_rpc.py#L292-L294 3. https://docs.openstack.org/developer/neutron/devref/ provisioning_blocks.html Cheers, Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170330/41c3d7b0/attachment.html>