Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1240852

Summary:	[RFE] NIC Config Templates Should Include MTU Settings
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	openstack-tripleo-heat-templates	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED ERRATA	QA Contact:	Omri Hochman <ohochman>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0 (Kilo)	CC:	athomas, bfournie, dsneddon, dtantsur, gregraka, hjensas, jcoufal, kbasil, mburns, oblaut, ohochman, racedoro, rhel-osp-director-maint, sasha
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.5.1-0.20190606110437.b9992d9.el8ost	Doc Type:	Enhancement
Doc Text:	In Red Hat OpenStack Platform 15, you can specify MTU (maximum transmission unit) settings for each network, and RHOSP will automatically write those settings to the network interface configuration templates. MTU values should be set in the network_data.yaml file. This enhancement alleviates the step of manually updating the network templates for each role, and reduces the likelihood of manual entry errors.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:15:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1386319

Description Dan Sneddon 2015-07-07 22:43:50 UTC

Description of problem:
The network interface templates for network isolation accept MTU settings for every interface, but it isn't clear how to set the MTU by looking at the sample files. They should include sample MTU (set to the default of 1500).

Version-Release number of selected component (if applicable):
poodle-2015-07-07

How reproducible:
100%

Steps to Reproduce:
1. Configure network isolation
2.
3.

Actual results:
You can add MTU settings, but you need to know what to add

Expected results:
There should be an MTU setting in the file that can just be changed.

Additional info:
This is really just a matter of including the defaults rather than not setting them. It will be more clear how to change the settings if we list the default MTU along with a comment explaining how to change it. I will patch the sample NIC config templates to include this setting and some comments.

Comment 5 Mike Burns 2016-04-07 20:43:53 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 8 Dmitry Tantsur 2016-12-12 15:14:20 UTC

We've discussed this report in the bug smash meeting, and agree that this sounds like an issue, not an RFE. I also don't believe that it's high priority, as it's mostly about missing documentation.

Comment 11 Nir Yechiel 2016-12-19 13:28:04 UTC

Dan, as the reporter of this BZ, can you clarify what MTU settings we have in the template today (as of Newton), and what work (if any) is still required?

Thanks,
Nir

Comment 12 Dan Sneddon 2016-12-19 18:03:57 UTC

(In reply to Nir Yechiel from comment #11)
> Dan, as the reporter of this BZ, can you clarify what MTU settings we have
> in the template today (as of Newton), and what work (if any) is still
> required?
> 
> Thanks,
> Nir

We don't currently set the mtu in any of our sample NIC templates, so it defaults to 1500. I can submit a patch that adds MTU to all the sample NIC templates. I'm not sure that will get approved, though, since I got some resistance to the idea when I brought it up for upstream discussion.

Comment 13 Bob Fournier 2018-02-19 17:04:15 UTC

Moving this flag to OSP-14 so we can discuss for inclusion.

Comment 30 errata-xmlrpc 2019-09-21 11:15:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811