excessive "no bound segment for port warnings" in server log

[Kevin Benton]

The server logs are filled with the warnings below in a normal tempest run. This is easy to trigger in a normal workflow by updating a port which is not yet bound to a host. For example, the following will result in a warning:

neutron port-create net --name=myport
neutron port-update myport --allowed-address-pairs type=dict list=true mac_address=01:02:03:04:05:06,ip_address=1.1.1.1/32

2016-03-09 20:06:55.986 18501 WARNING neutron.plugins.ml2.plugin [req-40c0c19d-41fb-41b3-bf53-a7025116c3b4 tempest-PortsIpV6TestJSON-136844784 -] In _notify_port_updated(), no bound segment for port 1438eb2e-e084-43e8-b8bd-552408bd8b02 on network 293447f0-5fbc-4cb7-8521-0c57ab3ab800
2016-03-09 20:06:58.922 18502 WARNING neutron.plugins.ml2.plugin [req-0c734344-da3c-4eca-b162-a0b3189e378e tempest-PortsIpV6TestJSON-136844784 -] In _notify_port_updated(), no bound segment for port f1a92580-9894-4bff-b2e2-feddcbf555d3 on network ab152352-b335-4a25-8458-675d48666cf1
2016-03-09 20:06:59.667 18502 WARNING neutron.plugins.ml2.plugin [req-2e7c62c6-e846-473c-9ad3-1b06db91fdc1 tempest-PortsIpV6TestJSON-136844784 -] In _notify_port_updated(), no bound segment for port f1a92580-9894-4bff-b2e2-feddcbf555d3 on network ab152352-b335-4a25-8458-675d48666cf1
2016-03-09 20:07:11.848 18502 WARNING neutron.plugins.ml2.plugin [req-ccd3058e-211b-4a42-9ca6-2200fde4f8e7 tempest-PortsIpV6TestJSON-136844784 -] In _notify_port_updated(), no bound segment for port 2e13552e-e9cb-479f-aea7-dba2613399a4 on network 293447f0-5fbc-4cb7-8521-0c57ab3ab800
2016-03-09 20:07:16.215 18502 WARNING neutron.plugins.ml2.plugin [req-0375d8af-8af2-46e2-bd9e-bdbcd095d29d tempest-PortsIpV6TestJSON-136844784 -] In _notify_port_updated(), no bound segment for port 40faa9e6-a606-48bc-91c7-ba31d586997a on network 293447f0-5fbc-4cb7-8521-0c57ab3ab800

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 54594b4fa0fe4f6fcc45f53b8ce19160d219f2df
Author: Kevin Benton <email address hidden>
Date: Thu Mar 10 14:58:31 2016 -0800

    ML2: Downgrade 'no bound segment' warning

    This is a normal occurence if a port is created and updated
    before it is actually bound to a host. It's not a warning
    condition because it doesn't mean anything is wrong.

    Change-Id: Ie1eb885f61e42dd7b24016adf3c02d4c504f6543
    Closes-Bug: #1555850

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/neutron 8.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/296530

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/296531

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/296530
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b90ca9f369731c716776a563f562ac82ead78188
Submitter: Jenkins
Branch: stable/liberty

commit b90ca9f369731c716776a563f562ac82ead78188
Author: Kevin Benton <email address hidden>
Date: Thu Mar 10 14:58:31 2016 -0800

    ML2: Downgrade 'no bound segment' warning

    This is a normal occurence if a port is created and updated
    before it is actually bound to a host. It's not a warning
    condition because it doesn't mean anything is wrong.

    Change-Id: Ie1eb885f61e42dd7b24016adf3c02d4c504f6543
    Closes-Bug: #1555850
    (cherry picked from commit 54594b4fa0fe4f6fcc45f53b8ce19160d219f2df)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/296531
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=506b87578a2b912cd407fd523c8401b9c7df137f
Submitter: Jenkins
Branch: stable/kilo

commit 506b87578a2b912cd407fd523c8401b9c7df137f
Author: Kevin Benton <email address hidden>
Date: Thu Mar 10 14:58:31 2016 -0800

    ML2: Downgrade 'no bound segment' warning

    This is a normal occurence if a port is created and updated
    before it is actually bound to a host. It's not a warning
    condition because it doesn't mean anything is wrong.

    Change-Id: Ie1eb885f61e42dd7b24016adf3c02d4c504f6543
    Closes-Bug: #1555850
    (cherry picked from commit 54594b4fa0fe4f6fcc45f53b8ce19160d219f2df)

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/neutron 2015.1.4 release.

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/neutron 7.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 2015.1.4 release.