https://bugzilla.suse.com/show_bug.cgi?id=1188915 Joerg Roedel <jroedel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |dracut-maintainers@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188915 https://bugzilla.suse.com/show_bug.cgi?id=1188915#c2 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #2 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Joerg Roedel from comment #1)

The issue is likely here in /usr/bin/dracut:

| # source our config file | if [[ -f $conffile ]]; then | check_conf_file "$conffile" | # shellcheck disable=SC1090 | . "$conffile" | fi | | # source our config dir | for f in $(dropindirs_sort ".conf" "$confdir" "$dracutbasedir/dracut.conf.d"); do | check_conf_file "$f" | # shellcheck disable=SC1090 | [[ -e $f ]] && . "$f" | done

The config file is sourced before the config directories. The directory which constains 01-dist.conf is even sourced last, so there is no way to overwrite the hostonly default set by the package.

I think the dist-defaults belong into /etc/dracut.conf so that users can replace/update them.

Indeed, that order looks wrong, the configs in /etc must be able to overwrite the vendor defaults. But the dist-defaults in /usr/lib/dracut/dracut.conf* is correct. /etc/dracut.conf* is for the admin not for the vendor. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188915 https://bugzilla.suse.com/show_bug.cgi?id=1188915#c4 --- Comment #4 from Joerg Roedel <jroedel@suse.com> --- (In reply to Antonio Feijoo from comment #3)

Although this behavior seems wrong, after reading the dracut documentation (https://mirrors.edge.kernel.org/pub/linux/utils/boot/dracut/dracut. html#dracutconf5), it's done on purpose.

--> dracut.conf is loaded during the initialisation phase of dracut. Command line parameter will override any values set here.

*.conf files are read from /usr/lib/dracut/dracut.conf.d and /etc/dracut.conf.d. Files with the same name in /etc/dracut.conf.d will replace files in /usr/lib/dracut/dracut.conf.d. The files are then read in alphanumerical order and will override parameters set in /etc/dracut.conf. --<

So, I think it will not be easy to convince upstream to change this order...

So I guess the distro default needs to be set in another place? It seems wrong to have no way of opting out of the hostonly setting. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188915 https://bugzilla.suse.com/show_bug.cgi?id=1188915#c6 --- Comment #6 from Joerg Roedel <jroedel@suse.com> --- (In reply to Antonio Feijoo from comment #5)

...

So I guess the distro default needs to be set in another place? It seems wrong to have no way of opting out of the hostonly setting.

Distro defaults can be overwritten using a configuration file with a name alphabetically greater than 01-dist.conf inside /etc/dracut.conf.d

E.g.:

$ cat /etc/dracut.conf.d/99-custom.conf hostonly="no" hostonly_cmdline="no"

Can you document that in /etc/dracut.conf? I find this behaviour not really intuitive. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188915 https://bugzilla.suse.com/show_bug.cgi?id=1188915#c8 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #8 from Antonio Feijoo <antonio.feijoo@suse.com> --- Closing it, as it's not really a bug. -- You are receiving this mail because: You are on the CC list for the bug.