Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The ospf6d component of quagga package allows specifying "per interface" distribution list, for example:
interface eth1.200
ipv6 ospf6 cost 1
ipv6 ospf6 hello-interval 10
ipv6 ospf6 dead-interval 40
ipv6 ospf6 retransmit-interval 5
ipv6 ospf6 priority 1
ipv6 ospf6 transmit-delay 1
ipv6 ospf6 instance-id 0
ipv6 ospf6 advertise prefix-list NONE
That declaration works well and it is possible to be saved through the vty console. But the problem appears when one are trying to start or restart the ospf6d daemon with the previous saved declaration - the daemon cannot be started. The problem can be reproduced for all versions of quagga package shipped with RHEL5/6.
Version-Release number of selected component (if applicable):
quagga-0.99.15-5.el6_0.2
How reproducible:
always
Steps to Reproduce:
1. Start ospfd
2. Connect to the vty console
$ telnet ::1 ospf6d
3. Setup ospf6 router, activate the interface, declare an appropriate prefix-list and set it in the interface prefix advertisement option:
>en
# con t
# ipv6 prefix-list NONE seq 5 deny any
# interface eth0
# ipv6 ospf6 advertise prefix-list NONE
# write
4. Stop and start (restart) ospfd
# service ospf6d restart
Actual results:
The daemon ospf6d cannot be started
Expected results:
The daemon ospf6d should be start normally
Additional info:
RHEL6 compiled osp6d does not produce backtrace screen output, but under RHEL5, the output looks like:
Starting ospf6d: OSPF6: Received signal 11 at 1325090168 (si_addr 0x48, PC 0xdaf7b1); aborting...
Program counter: ospf6d[0xdaf7b1]
Backtrace for 11 stack frames:
/usr/lib/quagga/libzebra.so.0(zlog_backtrace_sigsafe+0x51)[0x7ce8d1]
/usr/lib/quagga/libzebra.so.0(zlog_signal+0x21e)[0x7cef1e]
/usr/lib/quagga/libzebra.so.0[0x7de7d6]
[0xdf3440]
ospf6d[0xdaf7b1]
/usr/lib/quagga/libzebra.so.0(cmd_execute_command_strict+0x5dd)[0x7b79cd]
/usr/lib/quagga/libzebra.so.0(config_from_file+0x74)[0x7b9e44]
/usr/lib/quagga/libzebra.so.0(vty_read_config+0x147)[0x7b0627]
ospf6d(main+0x287)[0xd9fac7]
/lib/libc.so.6(__libc_start_main+0xdc)[0x188e9c]
ospf6d[0xd9f5b1]
Created attachment 555504[details]
This patch fixes issue with no advertise prefix-list
This seems to be known issue when there is specified
ipv6 ospf6 advertise prefix-list NONE
in the osfp6d.conf. I've tried to backport this patch that has fixed the issue for me.
Thank You, Jiri. I successfully recompiled Quagga package from src.rpm with Your patch applied. It works.
Is there any possibility for the patched version to be included in the bugfix stream of updates or we should wait for next minor release of RHEL 6?
(In reply to comment #3)
> Thank You, Jiri. I successfully recompiled Quagga package from src.rpm with
> Your patch applied. It works.
>
Thank you for test.
> Is there any possibility for the patched version to be included in the bugfix
> stream of updates or we should wait for next minor release of RHEL 6?
The quagga component have to be scheduled to be updated. I would recommend to request it through customer portal:
https://access.redhat.com/support/
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
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://rhn.redhat.com/errata/RHSA-2017-0794.html
Description of problem: The ospf6d component of quagga package allows specifying "per interface" distribution list, for example: interface eth1.200 ipv6 ospf6 cost 1 ipv6 ospf6 hello-interval 10 ipv6 ospf6 dead-interval 40 ipv6 ospf6 retransmit-interval 5 ipv6 ospf6 priority 1 ipv6 ospf6 transmit-delay 1 ipv6 ospf6 instance-id 0 ipv6 ospf6 advertise prefix-list NONE That declaration works well and it is possible to be saved through the vty console. But the problem appears when one are trying to start or restart the ospf6d daemon with the previous saved declaration - the daemon cannot be started. The problem can be reproduced for all versions of quagga package shipped with RHEL5/6. Version-Release number of selected component (if applicable): quagga-0.99.15-5.el6_0.2 How reproducible: always Steps to Reproduce: 1. Start ospfd 2. Connect to the vty console $ telnet ::1 ospf6d 3. Setup ospf6 router, activate the interface, declare an appropriate prefix-list and set it in the interface prefix advertisement option: >en # con t # ipv6 prefix-list NONE seq 5 deny any # interface eth0 # ipv6 ospf6 advertise prefix-list NONE # write 4. Stop and start (restart) ospfd # service ospf6d restart Actual results: The daemon ospf6d cannot be started Expected results: The daemon ospf6d should be start normally Additional info: RHEL6 compiled osp6d does not produce backtrace screen output, but under RHEL5, the output looks like: Starting ospf6d: OSPF6: Received signal 11 at 1325090168 (si_addr 0x48, PC 0xdaf7b1); aborting... Program counter: ospf6d[0xdaf7b1] Backtrace for 11 stack frames: /usr/lib/quagga/libzebra.so.0(zlog_backtrace_sigsafe+0x51)[0x7ce8d1] /usr/lib/quagga/libzebra.so.0(zlog_signal+0x21e)[0x7cef1e] /usr/lib/quagga/libzebra.so.0[0x7de7d6] [0xdf3440] ospf6d[0xdaf7b1] /usr/lib/quagga/libzebra.so.0(cmd_execute_command_strict+0x5dd)[0x7b79cd] /usr/lib/quagga/libzebra.so.0(config_from_file+0x74)[0x7b9e44] /usr/lib/quagga/libzebra.so.0(vty_read_config+0x147)[0x7b0627] ospf6d(main+0x287)[0xd9fac7] /lib/libc.so.6(__libc_start_main+0xdc)[0x188e9c] ospf6d[0xd9f5b1]