Migrate networks with MTU = 0 to a more reasonable value (1500?)

Bug #1556182 reported by Ihar Hrachyshka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Ihar Hrachyshka

Bug Description

In Mitaka, new networks are now created with default 1500 mtu (minus tunneling overhead). But for old networks, mtu value is left intact, meaning they are still affected by MTU mismatch issues. We should migrate those resources to use a saner value for the attribute.

Changed in neutron:
assignee: nobody → Ihar Hrachyshka (ihar-hrachyshka)
status: New → Confirmed
importance: Undecided → Medium
tags: added: linuxbridge ovs
Changed in neutron:
status: Confirmed → In Progress
Changed in neutron:
milestone: newton-2 → newton-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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

commit a984f9554cdcbe93c840a1d8f5c04302e9331e79
Author: Ihar Hrachyshka <email address hidden>
Date: Sat Jul 2 17:30:21 2016 +0200

    Calculate MTU on every network fetch instead of on create

    Today, existing networks may not reflect MTU configured for
    neutron-server, if they were created when neutron-server was using
    different MTU setup for its infrastructure, or when it was using bad
    default values for network MTUs (specifically, before Mitaka, all networks
    were getting MTU = 0 by default, disabling both advertisement and data
    path MTU size enforcement).

    This patch stops persisting MTU in the database on network create and
    instead calculate it on every network resource fetch.

    DocImpact Now changes to MTU configuration options immediately affect
              existing network MTUs, not just new networks.

    UpgradeImpact Existing networks with invalid MTU persisted in database
                  may change their MTU values to reflect configuration.

    Change-Id: Iee4f5037bf10b73ba98464143b183aacb59c22f2
    Closes-Bug: #1556182

Changed in neutron:
status: In Progress → Fix Released
tags: added: neutron-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/347067

tags: removed: neutron-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (stable/mitaka)

Change abandoned by Ihar Hrachyshka (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/347067
Reason: I don't plan to land it in Mitaka. I got what I needed from CI.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 9.0.0.0b3

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.