InvalidInput exceptions from DHCP RPC handler

[Kevin Benton]

Normal tempest runs are filled with exceptions in the DHCP RPC handler when it tries to create or update a port on a network that has its subnet deleted at the same time:

InvalidInput: Invalid input for operation: IP allocation requires subnets for network.

http://logs.openstack.org/82/346282/4/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/d4ea1f6/logs/screen-q-svc.txt.gz?level=TRACE

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/362343
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c05751a556a9124969de991ae226380b41a56502
Submitter: Jenkins
Branch: master

commit c05751a556a9124969de991ae226380b41a56502
Author: Kevin Benton <email address hidden>
Date: Sat Aug 27 03:25:27 2016 -0700

    Catch InvalidInput in DHCP port actions

    The exception handler checking for concurrently deleted subnets
    was missing InvalidInput, which comes from IPAM when a port creation
    request references a subnet that doesn't exist.

    This patch just catches that exception.

    Change-Id: I14f9e4bddde845e3fef2b0d8649d3954ba5c93bd
    Closes-Bug: #1618187

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 9.0.0.0b3 development milestone.