Bug 1917640 - NM cannot manage interface used by iscsi rootfs
Summary: NM cannot manage interface used by iscsi rootfs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-19 03:03 UTC by Sampson Fung
Modified: 2021-11-30 17:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:44:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sampson Fung 2021-01-19 03:03:40 UTC
Description of problem:
NM create new runtime connection on each reboot for the iscsi rootfs interface

Version-Release number of selected component (if applicable):
NetworkManager-1.26.4-1.fc33
kernel-5.10.7-200.fc33.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Using Server-netinst ISO to install to a iscsi rootfs
2.Boot into installed Fedora, note down the output of "nmcli con" after each boot

Actual results:
Fedora create a new runtime NM connection for the iscsi interface, not using any pre-existing system-connections


Expected results:
NM should use defined system-connection for that interface, to allow changing of interface otpions like wake-on-lan.


Additional info:
Same result for:
- fresh installation on baremetal Vs kvm guest
- fresh installation on tagged vlan Vs non-vlan of the iscsi interface
- fresh installation on single interface (for iscsi and Internet) Vs multiple (dedicated vlan interface for iscsi and Internet)

Discussed on Ask.fedoraproject.org
https://ask.fedoraproject.org/t/a-new-nm-connection-auto-created-after-reboot/11652

$cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vdaboot/vmlinuz-5.10.7-200.fc33.x86_64 root=UUID=uuiduuid-uuid-uuid-uuid-uuiduuiduuid ro rootflags=subvol=idaroot netroot=iscsi:@192.168.100.44::3260:iface0:vl100::iqn.2021-01.xxx.yyyy:zzzz rd.iscsi.initiator=iqn.2021-01.xxx.yyyy:zzzz ip=192.168.100.66:::255.255.255.0::vl100:none vlan=vl100:enp1s0

Comment 1 Ben Cotton 2021-11-04 16:17:08 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 2 Ben Cotton 2021-11-30 17:44:30 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.