NeutronBindNetworkPlugin multi segment mtu handling

Bug #1822099 reported by Maurice Escher on 2019-03-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Maurice Escher

Bug Description


with NeutronBindNetworkPlugin and multi segment networks, the neutron mtu value for network allocation is taken from the share network,
but the share network is updated with the mtu
only after the allocation is created.

As a result the mtu is empty on the first network allocation in
a share network. (And the next allocation takes the mtu value from the previous allocation)
And it is up to the driver what to do with this.

I know for example that the netapp driver takes a default mtu.
But I don't want the default, I want what is defined on the neutron net.


Fix proposed to branch: master

Changed in manila:
assignee: nobody → Maurice Escher (maurice-escher)
status: New → In Progress
Changed in manila:
milestone: none → train-1
importance: Undecided → Medium
Changed in manila:
assignee: Maurice Escher (maurice-escher) → Tom Barron (tpb)
Tom Barron (tpb) on 2019-05-13
Changed in manila:
assignee: Tom Barron (tpb) → Maurice Escher (maurice-escher)

Submitter: Zuul
Branch: master

commit bc87926e60bca11a1bc91dfaadb8e571a38c0e5f
Author: Maurice Escher <email address hidden>
Date: Thu Mar 28 11:22:02 2019 +0100

    NeutronBindNetworkPlugin: fix multi segment mtu

    Neutron mtu value for network allocation is taken from share network,
    so the share network needs to be updated with the mtu
    before the allocation is created.

    This prevents the mtu being empty on the first network allocation in
    a share network.

    Change-Id: I89de02af7d739bbe70f1d893cc2b6ced0157d120
    Closes-Bug: #1822099

Changed in manila:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers