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.

btw, when I say "debug logging", I mean "level=TRACE". No need to omit certain levels when we are debugging. Just turn on all we have.


Usually we can enable debug logging via NetworkManager.conf or at runtime with `nmcli general logging`.

When running in initrd via dracut, we also honor "rd.debug".


I think that still can be limiting. For example, you might build your own ramdisk without dracut, so rd.debug is not going to work. And a this point, it might be cumbersome to rebuild the ramdisk to enable debug logging.

Support a new kernel command line "nm.debug" which is interpreted by NetworkManager and which would set level=TRACE && domains=ALL (note that this "ALL" would exclude "VPN_PLUGIN" domain at higher level, as intended -- see `man NetworkManager.conf`).

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1297

fixed upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4ef40700c401d5d230a0ab727ba0f2f2dc3adaa4

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 (NetworkManager bug fix and enhancement update), 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-2022:8265