MTU settings for neutron

Bug #1620953 reported by satheeshprabhakaran.v on 2016-09-07
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-ansible
Medium
Kevin Carter

Bug Description

Code changes for setting MTU value for instance network interface.

Changed in openstack-ansible:
assignee: nobody → satheeshprabhakaran.v (vsp661992)
Changed in openstack-ansible:
status: New → Incomplete
Kevin Carter (kevin-carter) wrote :
Changed in openstack-ansible:
assignee: satheeshprabhakaran.v (vsp661992) → Kevin Carter (kevin-carter)
status: Incomplete → Confirmed
importance: Undecided → Medium

Reviewed: https://review.openstack.org/384635
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=08ceafa7ae53e9b8b0ccf893768c313ffbc52bc0
Submitter: Jenkins
Branch: stable/mitaka

commit 08ceafa7ae53e9b8b0ccf893768c313ffbc52bc0
Author: Kevin Carter <email address hidden>
Date: Mon Oct 10 12:07:45 2016 -0500

    Update the neutron MTU settings on upgrade

    Update the MTU setting for networks within neutron. When migrating from
    Liberty to Mitaka neutron does not automatically set or migrate networks.
    Neutron has no migration to correctly set the MTU on existing networks
    created in liberty or below. This work-around sets the MTU on these
    networks before the upgrade starts so that instances booted on these
    networks after the upgrade has finished will have their MTUs set
    correctly.

    Closes-Bug: #1620953
    Change-Id: I001f3b940089ccd55a932433c2563c143670a4d1
    Signed-off-by: Kevin Carter <email address hidden>

tags: added: in-stable-mitaka

This issue was fixed in the openstack/openstack-ansible 13.3.6 release.

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

Other bug subscribers