network_device_mtu not documented in agent config files
Bug #1504527 reported by
Ihar Hrachyshka
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
There is no network_device_mtu notion in agent config files, while it's a supported and useful option.
-bash-4.2$ grep network_device_mtu -r etc/
-bash-4.2$
Changed in neutron: | |
importance: | Undecided → Low |
status: | New → Confirmed |
tags: | added: l3-ipam-dhcp linuxbridge low-hanging-fruit ovs |
Changed in neutron: | |
assignee: | nobody → Jaiveek Shah (jaiveek-shah) |
tags: | added: juno-backport-potential kilo-backport-potential liberty-rc-potential |
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: |
added: liberty-backport-potential removed: liberty-rc-potential |
tags: | removed: juno-backport-potential |
Changed in neutron: | |
assignee: | Jaiveek Shah (jaiveek-shah) → nobody |
status: | In Progress → Confirmed |
Changed in neutron: | |
assignee: | nobody → Mohammad Shahid (mohammad-shahid1) |
tags: | removed: liberty-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
no longer affects: | neutron/kilo |
To post a comment you must log in.
Can I take a stab on this defect?