yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52061
[Bug 1576713] Re: Network metadata fails to state correct mtu
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/mitaka
Importance: Undecided
Status: New
** Changed in: nova/mitaka
Status: New => In Progress
** Changed in: nova/mitaka
Assignee: (unassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
** Changed in: nova/mitaka
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1576713
Title:
Network metadata fails to state correct mtu
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) mitaka series:
In Progress
Bug description:
Scenario:
Instance is booted on Neutron tenant network with ML2 OVS driver and
encapsulation. The MTU for that network is automatically calculated as
1450. Instance has --config-drive=true set.
Result:
In <config_drive>/openstack/latest/network_data.json we get:
"links": [{"ethernet_mac_address": "fa:16:3e:36:96:c8", "mtu": null,
"type": "ovs", "id": "tapb989c3aa-5c", "vif_id": "b989c3aa-5c1f-
4d2b-8711-b96c66604902"}]
Expected:
Have "mtu": "1450" instead.
Environment:
OpenStack Mitaka on Ubuntu 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1576713/+subscriptions
References