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.

Bug 1537160

Summary:	assertion failure "_device_activate: assertion 'nm_device_get_managed (self, FALSE)' failed"
Product:	Red Hat Enterprise Linux 7	Reporter:	Thomas Haller <thaller>
Component:	NetworkManager	Assignee:	Thomas Haller <thaller>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.5	CC:	aloughla, atragler, bgalvani, fgiudici, jreznik, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-18 13:04:59 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:

Description Thomas Haller 2018-01-22 15:19:06 UTC

somehow, I hit an assertion.

I think I:

  - had an external bridge device t-br0, I restarted NM and the device was marked 
    as unmanaged.
  - I tried to activate a connection for the bridge, which failed with an error
    that there is no suitable device. I think that is already a bug, activating 
    a connection on an unmanaged bridge, should make it managed.
  - then I deleted the bridge with `nmcli device delete`
  - then I tried to activate the connection again, and hit the assertion.

Tested master, 1.11.1-19479.a0cf466482.fc27

Comment 3 Thomas Haller 2018-02-06 10:45:35 UTC

I was unable to produce the crash, but at least the logfile is helpful.

I propose th/device-activation-fix-rh1537160.

Please review.

Comment 5 Beniamino Galvani 2018-02-07 07:41:39 UTC

> core/trivial: add comment in set_property() for construct-only properties

The comment should be added to the VPN property as well.

The rest LGTM.

Comment 6 Thomas Haller 2018-02-07 14:28:12 UTC

merged upstream:

master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=665d47466a16f57affa329e70b39648c7b104141

nm-1-10: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=167ca04f3799389a25420d275b1fb7954f95a722



I still failed to find a reproducer. For now, I assume that the patches fix the assertion failure. Will try more to find reproducer.

Comment 8 Thomas Haller 2018-06-18 13:04:59 UTC

Since there is no clear reproducer, and a possibly mitigation is performed, I am closing this as WORKSFORME.

Let's hunt down bugs that we know that they actually exist. Instead of tracking an internally found issue, where it's unclear whether it's still there.