Created attachment 1231095 [details]
Description of problem:
NetworkManager occasionally runs into an assertion failure during the Cockpit integration tests.
NetworkManager:ERROR:devices/nm-device.c:8954:<unknown-fcn>: assertion failed: (<dropped>)
Core and logs are attached.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run the check-networking script of Cockpit a couple hundred times for rhel-7 and wait for the core dump...
Created attachment 1231096 [details]
nm_device_start_ip_check (NMDevice *self)
NMDevicePrivate *priv = NM_DEVICE_GET_PRIVATE (self);
==> g_assert (priv->ip4_state == IP_DONE || priv->ip6_state == IP_DONE);
The crash should be fixed by the following upstream commit:
Instances of this failure are being tracked by the Cockpit integration tests here: https://github.com/cockpit-project/cockpit/issues/5662
Seems like a similar issue on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1409896
(In reply to Stef Walter from comment #4)
> Instances of this failure are being tracked by the Cockpit integration tests
> here: https://github.com/cockpit-project/cockpit/issues/5662
Would it be possible to give me a reproducer? I would like to implement this to master tests so no regression in this area occurs for you.
(In reply to Vladimir Benes from comment #7)
> Would it be possible to give me a reproducer? I would like to implement this
> to master tests so no regression in this area occurs for you.
No, not easily, unfortunately.
(In reply to Marius Vollmer from comment #9)
> (In reply to Vladimir Benes from comment #7)
> > Would it be possible to give me a reproducer? I would like to implement this
> > to master tests so no regression in this area occurs for you.
> No, not easily, unfortunately.
Actually starting `dnsmasq --interface eth1` and then upping ipv4.method shared connection on the eth1 device reproduces it. Two test cases added to prevent such crashes in the future.
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.