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:
Auto default wired connection are usually created on managed devices when no other profile has even been configured before.
If a connection has been defined by the user, in most scenarios, even when that custom profile is deleted, the auto default connection will not be created.
However, in cases where the device is in `unavailable` or `disconnected` state, it will be created.
This behaviour is not consistent and causes unintentional configuration to be applied on a device when the user actually wanted to delete/deactivate.
Ref:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/nm-manager.c?id=b10a7e5786e9c6bb95bd014ee165b452c247da6d#n1474
Version-Release number of selected component (if applicable):
How reproducible:
30%
Steps to Reproduce:
It has been reproduced periodically through the nmstate integration tests.
1. Delete an active profile.
2. The default profile is auto generated.
Actual results:
The default profile is auto generated.
Expected results:
The default profile should no be auto generated.
Additional info:
could you give me some reproducer?
I am a bit lost in how to make difference between 1.22 and 1.26.
I have no connection for eth8, I don't have NM-config-server installed
systemctl restart NetworkManager
nmcli connection delete id Wired\ connection\ 1
rm -rf /var/lib/NetworkManager/no-auto-default.state
nmcli con add type ethernet ifname eth8 con-name con_general
nmcli con up con_general
sleep 1
nmcli con down con_general
sleep 1
nmcli device set eth8 managed no
nmcli device set eth8 managed yes
sleep 2
nmcli con del con_general
sleep 1
nmcli con
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-2020:4499