Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1840232 - NetworkManager Profile Persistence
Summary: NetworkManager Profile Persistence
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IoT
TreeView+ depends on / blocked
 
Reported: 2020-05-26 15:35 UTC by Andrew G. Dunn
Modified: 2021-05-25 16:20 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 16:20:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Andrew G. Dunn 2020-05-26 15:35:41 UTC 
Description of problem: On Fedora IoT (32) I am interested in creating a specific profile for my onboard ethernet adapter. It appears that each time the system boots NetworkManager will create a profile automagically for that interface, so no changes via `nmcli` will take effect between reboots.


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


How reproducible: I've reproduced on two Fedora IoT fresh installs.


Steps to Reproduce:

```
[root@arbiter ~]# nmcli 
eno1: connected to Wired Connection
        "Intel Ethernet"
        ethernet (e1000e), F4:4D:30:6D:86:55, hw, mtu 1500
        ip4 default
        inet4 172.16.0.8/24
        route4 0.0.0.0/0
        route4 172.16.0.0/24
        inet6 fe80::f64d:30ff:fe6d:8655/64
        route6 fe80::/64
        route6 ff00::/8

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 172.16.0.1
        interface: eno1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[root@arbiter ~]# nmcli connection delete Wired\ Connection 
Connection 'Wired Connection' (4659b5fe-044f-447a-9eeb-14b38d491efb) successfully deleted.
[root@arbiter ~]# nmcli connection reload 
[root@arbiter ~]# nmcli 
eno1: connected to onboard
        "Intel Ethernet"
        ethernet (e1000e), F4:4D:30:6D:86:55, hw, mtu 1500
        ip4 default
        inet4 172.16.0.8/24
        route4 172.16.0.0/24
        route4 0.0.0.0/0

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[root@arbiter ~]# reboot

Session terminated, killing shell... ...killed.
Terminated
[agd@arbiter ~]$ Connection to 172.16.0.8 closed by remote host.
Connection to 172.16.0.8 closed.
[agd@enoch ~]$ ssh 172.16.0.8
Last login: Tue May 26 11:24:37 2020 from 172.16.0.50
[agd@arbiter ~]$ su root
Password: 
[root@arbiter agd]# cd
[root@arbiter ~]# nmcli
eno1: connected to Wired Connection
        "Intel Ethernet"
        ethernet (e1000e), F4:4D:30:6D:86:55, hw, mtu 1500
        ip4 default
        inet4 172.16.0.8/24
        route4 0.0.0.0/0
        route4 172.16.0.0/24
        inet6 fe80::f64d:30ff:fe6d:8655/64
        route6 fe80::/64
        route6 ff00::/8

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: 172.16.0.1
        interface: eno1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
```


Actual results: "Wired Connection", although deleted previously... is now newly created upon boot (checking the timestamp shows it was created during the boot process).

Expected results: System would "respect" the deletion of the automatic profile and begin using the manually specified profile.


Additional info:
Comment 1 Matthew Krupcale 2020-05-26 15:50:48 UTC 
It's possible this is related to an issue[1] I found on F32 Server after upgrading from F31. My guess is that this automatic profile is generated as a result of NM trying to replicate a previously existing connection during boot, although I don't know how the IoT boot process works. This generated profile then overrides the manually created profiles.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1829461
Comment 2 Fedora Program Management 2021-04-29 16:28:02 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Ben Cotton 2021-05-25 16:20:54 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.