yahoo-eng-team team mailing list archive

[OpenStack Infra <1618694@xxxxxxxxxxxxxxxxxx>]

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 <armamig@xxxxxxxxx>
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


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1618694

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

Status in neutron:
  Fix Released

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1618694/+subscriptions