Public bug reported:
This is needed because Neutron allows to change MTU values for networks
(through configuration options modification and neutron-server restart).
Without that, there is no way to apply new MTU for DHCP and router ports
without migrating resources to other nodes.
I suggest we apply MTU on conseqent plug() attempts, even if port
exists.
** Affects: neutron
Importance: Medium
Assignee: Ihar Hrachyshka (ihar-hrachyshka)
Status: Confirmed
** Affects: nova
Importance: Undecided
Status: New
** Tags: l3-ipam-dhcp linuxbridge ovs
** Tags added: l3-ipam-dhcp linuxbridge ovs
** Changed in: neutron
Importance: Undecided => Medium
** Changed in: neutron
Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)
** Changed in: neutron
Status: New => Confirmed
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1649845
Title:
Interface drivers don't update port MTU if the port already exists
Status in neutron:
Confirmed
Status in OpenStack Compute (nova):
New
Bug description:
This is needed because Neutron allows to change MTU values for
networks (through configuration options modification and neutron-
server restart). Without that, there is no way to apply new MTU for
DHCP and router ports without migrating resources to other nodes.
I suggest we apply MTU on conseqent plug() attempts, even if port
exists.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1649845/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
