NeutronBindNetworkPlugin multi segment mtu handling

Bug #1822099 reported by Maurice Escher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
Maurice Escher

Bug Description

Hi,

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.

BR,
Maurice

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.openstack.org/648387

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)
Changed in manila:
assignee: Tom Barron (tpb) → Maurice Escher (maurice-escher)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.opendev.org/648387
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=bc87926e60bca11a1bc91dfaadb8e571a38c0e5f
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/670410

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

This issue was fixed in the openstack/manila 9.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (stable/stein)

Reviewed: https://review.opendev.org/670410
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=677bb330bf302649a85bb3ae590b61df0a045685
Submitter: Zuul
Branch: stable/stein

commit 677bb330bf302649a85bb3ae590b61df0a045685
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
    (cherry picked from commit bc87926e60bca11a1bc91dfaadb8e571a38c0e5f)

tags: added: in-stable-stein
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 8.1.0

This issue was fixed in the openstack/manila 8.1.0 release.

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.