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/be55c62630aa05429d35ba489211efb03b167405/

looks related to https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=479ad5065e96abe4588c52c9588faf046cc182d1

... over to Lubomir.

Created attachment 1274350 [details]
A fix

(In reply to Lubomir Rintel from comment #2)
> Created attachment 1274350 [details]
> A fix

Let's not remove clearing needs_ip6_subnet in _cleanup_generic_post(). 

Let's properly clear the state during cleanup. Even if you can prove that it is actually always FALSE at that point, it's non obvious.


otherwise, lgtm

(switched a cleanup to a nm_assert(); i guess that makes more sense to make it explicit that the needs_subnet should be false at that point rather than an useless assignment)

master: 3e076cf8b1eba4937e1462d2ca34b9a65f500aff
nm-1-8: af87569a9bc0338ccaf7337f04dc8f3c3e04be4d

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/RHSA-2017:2299