OVN Neutron network MTU never get applied
Bug #1816449 reported by
Lucas Alvares Gomes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
High
|
Kamil Sambor |
Bug Description
Reported at https:/
Basically when you update the MTU from a Neutron network, that change is not being propagated to OVN. The reason is because OVN sets the MTU in the DHCP_Options table (which translates to Neutron subnets) and updating the network in Neutron does not triggers an update to the DHCP_Options table (only to the Logical_Switch one).
How to reproduce
1. Update the MTU in the Neutron network:
$ openstack network set --mtu 1400 TENANT_NET
2. Check the changes in OVN:
$ ovn-nbctl list DHCP_Options
You will see that it hasn't changed in OVN.
Changed in networking-ovn: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in networking-ovn: | |
assignee: | nobody → Kamil Sambor (ksambor) |
Changed in networking-ovn: | |
status: | Confirmed → In Progress |
tags: | added: networking-ovn-proactive-backport-potential |
tags: | removed: networking-ovn-proactive-backport-potential |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/645483 /git.openstack. org/cgit/ openstack/ networking- ovn/commit/ ?id=1daffa9634a 813ccbcf00a4c4c 9dbd2c504d326d
Committed: https:/
Submitter: Zuul
Branch: master
commit 1daffa9634a813c cbcf00a4c4c9dbd 2c504d326d
Author: Kamil Sambor <email address hidden>
Date: Fri Mar 22 07:53:47 2019 +0100
Propagate mtu to all subnets
In networking-ovn we map subnets to OVN DHCP_Options
rows (where we store the MTU), but from neutron API perspective,
the MTU is applied per network. So we need update all subnets
thats belong to network to propagade correctly MTU for network.
Closes-Bug: #1816449 f84316f9ee908e8 84539c7ed39
Change-Id: Ieddc16e607bcce