Bug 1425818

Summary: [abrt] [faf] NetworkManager: unknown function(): /usr/sbin/NetworkManager killed by 5
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: aloughla, atragler, bgalvani, fgiudici, lrintel, mleitner, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/be55c62630aa05429d35ba489211efb03b167405/
Whiteboard:
Fixed In Version: NetworkManager-1.8.0-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 09:24:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A fix none

Description Vladimir Benes 2017-02-22 14:02:58 UTC
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/

Comment 2 Lubomir Rintel 2017-04-26 17:47:30 UTC
Created attachment 1274350 [details]
A fix

Comment 3 Thomas Haller 2017-04-26 17:58:50 UTC
(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

Comment 4 Lubomir Rintel 2017-04-27 13:46:07 UTC
(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

Comment 6 errata-xmlrpc 2017-08-01 09:24:38 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, 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