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.

This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/ce4bfb94c491757e19887e6af81db862fe6a1ea3/

the issue here is a stack-overflow due to (unlimited) recursive calls of

  ip6_config_merge_and_apply (nm-device.c)
  nm_device_set_ip6_config (nm-device.c)
  device_ip6_config_changed (nm-policy.c)
  update_ip6_dns (nm-policy.c)
  nm_device_copy_ip6_dns_config (nm-policy.c)
  ip6_config_merge_and_apply (nm-device.c)
  ...


I think the immediate issue should be fixed by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=4adda2b79a946c41ef03239e3060c94b1c114cc9 (and all test failures so far pre-date this commit).



We still should avoid unbound recursion. In this case it was introduced by IPv6 prefix-delegation (https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=ec12fcf6bf4f306d426271c286db3c28b7025ba4), hence, over to Lubomir :)

Mass-moving bugs RHEL <= 7.6.0 to 7.7.0.
As we are past RFE deadline for 7.7.0 and we should have no new features on 7.8.0, please evaluate if it's still wanted on RHEL7 and contact PM for exception. You may also move it to RHEL8 if that's wanted. Thanks!

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/441

FAF hasn't reported any more issues lately, we do consider this fixed.

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 (NetworkManager bug fix and enhancement update), 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:4499