Bug 1303272

Summary:	quagga starts after networking but ospf6d doesn't use the autodetect MTU
Product:	Red Hat Enterprise Linux 7	Reporter:	Matyas Koszik <koszik>
Component:	quagga	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	kvolny, thozza
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-06 16:09:28 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:

Description Matyas Koszik 2016-01-30 03:46:59 UTC

Description of problem:
ospf6d uses MTU seen during initialization, which happens before networking, so it ignores the one set in the configuration.

Version-Release number of selected component (if applicable):
quagga-0.99.22.4-4.el7.x86_64

How reproducible:
very


Steps to Reproduce:
1. echo MTU=9000 >> /etc/sysconfig/network-scripts/ifcfg-enp7s0f0
2. echo -n 'router ospf6\ninterface enp7s0f0 area 0.0.0.0' > /etc/quagga/ospf6d.conf
3. reboot


Actual results:
sh ipv6 ospf int shows this:
Instance ID 0, Interface MTU 1500 (autodetect: 9000)
1500 is being used in the database description packets, making it impossible to peer with routers that check the mtu settings (which is the default, even in quagga).


Expected results:
Either the networking setup should occur before starting quagga, so changes like this are seen during initialization, or ospf6d should use the actual detected MTU.

Additional info:

Comment 2 Tomáš Hozza 2019-12-06 16:09:23 UTC

Red Hat Enterprise Linux version 7 entered the Maintenance Support 1 Phase in August 2019. In this phase only qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. Other errata advisories may be delivered as appropriate.

This bug has been reviewed by Support and Engineering representative and does not meet the inclusion criteria for Maintenance Support 1 Phase. If this issue still exists in newer major version of Red Hat Enterprise Linux, it has been cloned there and work will continue in the cloned bug.

For more information about Red Hat Enterprise Linux Lifecycle, please see https://access.redhat.com/support/policy/updates/errata/

Comment 3 RHEL Program Management 2019-12-06 16:09:28 UTC

Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain  the issue receives the proper prioritization with product and development management.

https://www.redhat.com/support/process/production/#howto