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.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
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.
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
(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.
Moving this flag to OSP-14 so we can discuss for inclusion.
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