RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1997603 - ospfd not running with ospf opaque-lsa option used
Summary: ospfd not running with ospf opaque-lsa option used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: frr
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-25 13:51 UTC by František Hrdina
Modified: 2022-05-17 12:35 UTC (History)
1 user (show)

Fixed In Version: frr-8.0-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:26:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-95572 0 None None None 2021-08-30 10:30:40 UTC
Red Hat Product Errata RHBA-2022:2310 0 None None None 2022-05-17 12:26:43 UTC

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


Note You need to log in before you can comment on or make changes to this bug.