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.

Description of problem:

NM.DeviceBridge.get_slaves() is not reporting unmanaged slaves.

Version-Release number of selected component (if applicable):

NetworkManager 1.22.8

How reproducible:

100%

Steps to Reproduce:
1. create a bridge
2. ip link add dummy0 type dummy
3. ip link set dummy0 up
4. nmcli dev set dummy0 managed no
5. ip link set dummy0 master br0

Actual results:

NM.DeviceBridge.get_slaves() is returning an empty list.

Expected results:

The list should contain the NM.Device of the slave.

Fernando, is this still important for Nsmtate when it is using Nispor?

Closing as nmstate does not require NetworkManager on querying kernel interface information any more.

If you still want to fix this, please open new bug and state the new use case.