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.
Bug 1687937 - Auto default wired connections should not be created if a custom one was already defined
Summary: Auto default wired connections should not be created if a custom one was alre...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 17:11 UTC by Edward Haas
Modified: 2020-11-04 01:49 UTC (History)
10 users (show)

Fixed In Version: NetworkManager-1.25.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:48:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
eth1-profile-is-auto-created (51.54 KB, application/x-xz)
2019-03-12 17:13 UTC, Edward Haas 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:49:06 UTC

Description Edward Haas 2019-03-12 17:11:37 UTC 
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:
Comment 2 Edward Haas 2019-03-12 17:13:41 UTC 
Created attachment 1543298 [details]
eth1-profile-is-auto-created
Comment 4 Thomas Haller 2020-03-25 15:09:30 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/450
Comment 5 Thomas Haller 2020-03-28 10:03:38 UTC 
fixed on master https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/ff814923ebfa434ba0ffaa13f0d61a4bb8ad6ec4
Comment 9 Vladimir Benes 2020-06-22 16:09:48 UTC 
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
Comment 10 Thomas Haller 2020-06-22 17:06:59 UTC 
(In reply to Vladimir Benes from comment #9)
> could you give me some reproducer?

resolved via IRC (isn't that right?)
Comment 11 Vladimir Benes 2020-06-23 08:04:16 UTC 
(In reply to Thomas Haller from comment #10)
> (In reply to Vladimir Benes from comment #9)
> > could you give me some reproducer?
> 
> resolved via IRC (isn't that right?)

yes yes, test added:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/585
Comment 14 errata-xmlrpc 2020-11-04 01:48:18 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.