Description of problem: I'm using Clevis to automatically unlock my laptop at boot when it's connected to my dock which has a wired connection. This causes an IP address to be setup in the initramfs through network-manager dracut module. The network interface always gets a different UUID, which makes it impossible to reconfigure the interface after switching root, because my ifcfg-XXX file has another UUID specified which never matches the one allocated in the initramfs. This makes NetworkManager show 2 different UUIDs for same physical interface, and of course the wrong one (the one from the boot) is configured. This is a hard requirement, typically I need to set up the DOMAIN search there + need to specify ETHTOOL_OPTS options because the dock interface is quite broken and doesn't initialize with expected speed. Question: is there a way to have the ifcfg file be in sync with the boot interface auto-generated configuration/UUID or be able to specify a UUID for the boot interface? Version-Release number of selected component (if applicable): NetworkManager-1.26.4-1.fc33.x86_64 How reproducible: Always on my system.
How do you change the setting with nmcli that you would like to have different in the system?
I'm using a ifcfg property to apply the domain: /etc/sysconfig/network-scripts/ifcfg-Ethernet_Dock: ~~~ [...] DOMAIN="libvirt home" ~~~ This is closely related to BZ #1934122 open on RHEL8 recently.
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.
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.