Bug 1997603

Summary:	ospfd not running with ospf opaque-lsa option used
Product:	Red Hat Enterprise Linux 9	Reporter:	František Hrdina <fhrdina>
Component:	frr	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED ERRATA	QA Contact:	František Hrdina <fhrdina>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	fhrdina
Target Milestone:	rc	Keywords:	AutoVerified, Patch, Reproducer, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	frr-8.0-4.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 12:26:41 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 František Hrdina 2021-08-25 13:51:54 UTC

Description of problem:
When the option ospf opaque-lsa is used in configuration file, the ospfd is not started

Version-Release number of selected component (if applicable):
frr-8.0-3.el9.

How reproducible:
always

Steps to Reproduce:
1. Enable ospfd in /etc/frr/daemons
2. Use this configuration with the correct ROUTER_ID in /etc/frr/frr.conf
hostname ROUTER1
password zebra
log file /var/log/frr/ospfd.log
!
!
router ospf
 ospf router-id ROUTER_ID
 network 10.0.0.0/8 area 0
 network 192.168.101.0/24 area 1
 ospf opaque-lsa
!
line vty

3. Create dummy interface
ip link add dummy1 type dummy
ip address add 192.168.101.1/24 dev dummy1
ip link set dummy1 up

4. service frr start
5. service frr status

Actual results:
ospfd is not running, it is not mentioned in running process in service frr status output, and also if you try run  
vtysh -c 'show ip ospf database

you get error that ospfd is not running



Expected results:
Ospfd should be started and be running
output of service frr status should contain information that ospfd is running

/usr/libexec/frr/ospfd -d -F traditional -A 127.0.0.1

Comment 27 errata-xmlrpc 2022-05-17 12:26:41 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 (new packages: frr), 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/RHBA-2022:2310