Pavel Valena
Pavel Valena
Probably related to: https://bugzilla.redhat.com/show_bug.cgi?id=2099256#c3
This might be just an issue in nfs-utils (`50-nfs.conf`).
It seems we've encountered this as well. - Wouldn't `nmcli device disconnect $DEVICE; dracut -f` workaround preserving the state of the device? Is there any way of not activating the...
> It seems we've encountered this as well. > > * Wouldn't `nmcli device disconnect $DEVICE; dracut -f` workaround preserving the state of the device? Is there any way of...
What I've found is that NetworkManager saves the devices which should not be used/autocreated in `/var/lib/NetworkManager/no-auto-default.state` .... dracut should probably respect that. _ _ _ _ **EDIT:** on my system...
* Meaning the file should probably copied and read by `/usr/libexec/nm-initrd-generator`
Please fix the CI issue: `Error: commit_message:1:1: error: use of type tag that's neither 'feat', 'fix' nor whitelisted (build, chore, ci, docs, perf, refactor, revert, style, test, improvement)` Otherwise LGTM.
> The "Resolves: rhbz#..." thing only works for automatic updates. For normal or side-tag updates the user is supposed to manually add the bugs, since they already have to manually...
I see- this does not work for stable Fedora updates as well, then- it wouldn't be limited to side-tags, but more of a general UX enhancement.