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.

Hi,

I tried to reproduce the problem but I couldn't find the conditions to trigger it.

Would it be possible to get a trace log? To capture it, set 'level' to TRACE in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart the NetworkManager service, reproduce and then attach the output of `journalctl -b`. Thanks

> Is this related to https://bugzilla.redhat.com/show_bug.cgi?id=2092323?

No, that one is in nmcli, this is in the daemon.

(In reply to Beniamino Galvani from comment #3)
> Hi,
> 
> I tried to reproduce the problem but I couldn't find the conditions to
> trigger it.
> 
> Would it be possible to get a trace log? To capture it, set 'level' to TRACE
> in the [logging] section of /etc/NetworkManager/NetworkManager.conf, restart
> the NetworkManager service, reproduce and then attach the output of
> `journalctl -b`. Thanks
> 

Howdy,

I have asked the customer and will upload when they provide `journalctl -b`.

Leaving needinfo for me.

Regards

Jon

This bug has been scheduled for migration to Jira (https://issues.redhat.com).

Please, let me know if you face any problems once it is done (Jira login creation, etc.). 

For guidance about your Jira account or creating one if needed, use the following KB articles: KB0016394, KB0016694, KB0016774.