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:
IPv6 RA timeout is derived from /proc/sys/net/ipv6/conf/$dev/router_solicitations * /proc/sys/net/ipv6/conf/$dev/router_solicitation_interval. But is clamped between 30 and 120 secs.
Version-Release number of selected component (if applicable):
NetworkManager-1.22.0-2.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create dummy interface
1. Set router_solicitations and router_solicitation_interval to 15 for the dummy
2. Enable RA via NetworkManager for the dummy
Actual results:
RA timeout is set for 120 secs
Expected results:
RA timeout 225
Additional info:
Comment 3Beniamino Galvani
2020-01-30 14:49:25 UTC
Comment 4Beniamino Galvani
2020-01-31 12:47:01 UTC
(In reply to RHEL Program Management from comment #2)
> Answer the following 3 questions:
> 1. What is the scope of harm if this BZ is not resolved in this release?
> Reviewers want to know which RHEL features or customers are affected and if
> it will impact any Layered Product or Hardware partner plans.
This bug badly impacts RHV as it breaks connectivity for VMs.
> 2. What are the risks associated with resolving this BZ? Reviewers want to
> know the scope of retesting, potential regressions
The fix is simple and self-contained, it doesn't impact other parts of code except IPv6 RA. We have 900+ tests in CI that covers many features, including IPv6 RA, so the regression risk is very low.
> 3. Provide any other details that meet blocker criteria or should be weighed
> in making a decision (Other releases affected, upstream status, business
> impacts, etc).
The bug is already fixed upstream.
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/RHBA-2020:1847