Red Hat Bugzilla – Bug 1478663
Weird concatenation of variable values from files in /etc/dracut.conf.d
Last modified: 2018-05-03 04:24:27 EDT
Description of problem:
Values of the same variable entered in multiple files in /etc/dracut.conf.d are concatenated as "value1value2"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. echo "add_drivers+=\"raid1\"" > /etc/dracut.conf.d/mdraid.conf
2. echo "add_drivers+=\"i915\"" > /etc/dracut.conf.d/gpu.conf
3. dracut -v -f -M
Final 17 lines, 1st line most important:
dracut-install: Failed to find module 'i915raid1'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.4N51Y8/initramfs --kerneldir /lib/modules/4.11.11-300.fc26.x86_64/ -m i915raid1
dracut: *** Installing kernel module dependencies ***
dracut: *** Installing kernel module dependencies done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done***
dracut: *** Hardlinking files ***
dracut: *** Hardlinking files done ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing GenuineIntel.bin ****
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut: No dracut internal kernel commandline stored in the initramfs
dracut: *** Creating image file '/boot/initramfs-4.11.11-300.fc26.x86_64.img' ***
dracut: *** Creating initramfs image file '/boot/initramfs-4.11.11-300.fc26.x86_64.img' done ***
Modules to load: 'i915 raid1'. Not 'i915raid1'.
The man page dracut.conf(5) shows to add spaces around the parameters.
1. echo "add_drivers+=\" raid1 \"" > /etc/dracut.conf.d/mdraid.conf
2. echo "add_drivers+=\" i915 \"" > /etc/dracut.conf.d/gpu.conf
3. dracut -v -f -M
"Space separated" I just got as spaces between module names - separated by spaces. Ok, must be space at the start, space separating names and space at the end.
I apologize for my misunderstood.
So, "bug" can be closed now.
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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'
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 26 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.