yahoo-eng-team team mailing list archive

[OpenStack Infra <1549471@xxxxxxxxxxxxxxxxxx>]

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

commit b2d0985d05013bf63eb965f3e5c934c558ea9f0d
Author: Sean M. Collins <sean@xxxxxxxxxxxxx>
Date:   Wed Feb 24 16:00:12 2016 -0500

    ML2: Increase segment_mtu from 0 to 1500 bytes
    
    Neutron should return sane MTU values in the API. A Neutron Network
    that has an MTU of zero wouldn't actually be a useful network, because
    nothing could ever be transmitted. Zero is a junk value, so let's
    replace it with standard ethernet MTU, which is a more believable value
    to return to users.
    
    Change-Id: I6a10c4dfc1f2198667f3d02528e2ca8020cb5bb8
    Closes-Bug: #1549471


** 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/1549471

Title:
  Networks with an MTU of zero makes zero sense

Status in neutron:
  Fix Released

Bug description:
  vagrant@vagrant-ubuntu-wily-32:~/devstack$ neutron net-show a99a3d30-19a0-4e69-9e90-129d192e5948
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | availability_zone_hints   |                                      |
  | availability_zones        | nova                                 |
  | id                        | a99a3d30-19a0-4e69-9e90-129d192e5948 |
  | is_default                | False                                |
  | mtu                       | 0                                    |
  | name                      | public                               |
  | port_security_enabled     | True                                 |
  | provider:network_type     | flat                                 |
  | provider:physical_network | default                              |
  | provider:segmentation_id  |                                      |
  | router:external           | True                                 |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   | f83007e9-0907-488b-9a45-940984d1f4dc |
  |                           | 2cb54543-2302-4142-8f3b-735fd5aa73fb |
  | tenant_id                 | f8190c1517b7455a89dc952d43f890eb     |
  +---------------------------+--------------------------------------+

  
  So yeah let's try and clean this up somehow. I imagine that part of it has to be the physical_network_mtus setting

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