Bug 1689054

Summary: libnm crash on `NM.Client.props.dns_configuration`
Product: Red Hat Enterprise Linux 7 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: atragler, bgalvani, fgiudici, fpokryvk, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: 7.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.18.0-0.3.20190408git43d9187c14.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:16:46 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
Reproduce script. none

Description Gris Ge 2019-03-15 03:32:52 UTC
Created attachment 1544252 [details]
Reproduce script.

Description of problem:

The `nmclient.get_dns_configuration()` works well while `nmclient.props.dns_configuration` cause sigfault.

Version-Release number of selected component (if applicable):
NetworkManager-libnm-1.12.0-8.el7_6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run attached python script after installed `python-gobject-base`
2. 
3.

Actual results:

Crash

Expected results:

No crash.

Additional info:

Comment 1 Beniamino Galvani 2019-03-18 09:14:42 UTC
This is fixed upstream in NM 1.16+. The fix will land in RHEL 7.7 with the rebase of NM.

Comment 4 errata-xmlrpc 2019-08-06 13:16:46 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/RHBA-2019:2302