Failed to determine MTU for segment None:None; network <net-id> MTU calculation may be not accurate

[Armando Migliaccio]

This is emitted under normal conditions. The trace is associated to another debug message that states the network has no segments.

http://logs.openstack.org/32/363332/3/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/8193aaa/logs/screen-q-svc.txt.gz?#_2016-08-31_03_58_03_400

This run has 500+ traces:

http://logs.openstack.org/32/363332/3/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/8193aaa/logs/screen-q-svc.txt.gz?level=TRACE

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit e5155fc483048ebf365e29104a928c19403a87bc
Author: Armando Migliaccio <email address hidden>
Date: Tue Aug 30 22:00:25 2016 -0700

    Do not warn under normal network circumstances

    If the network has no segment associated at a particular
    point of its lifecycle, there is no need to emit a warning,
    as the operator can do very little with the information
    given.

    Change-Id: I1263be60c3d73f7825596f5e8e7b918d8076f537
    Closes-bug: #1618694

[OpenStack Infra (hudson-openstack)]

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