Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
While it is documented that --include can only be used once on a dracut command line. This fact is easy to overlook and instead of emitting a comprehensible error message mkinitrd behaves in a difficult to explain way when there are multiple --include command lines supplied.
For example when I was testing something with kdump.
Sep 20 14:44:18 opal1 kdumpctl[158175]: Rebuilding /boot/initramfs-3.10.0-493.el7.x86_64kdump.img
Sep 20 14:44:19 opal1 dracut[160390]: Executing: /usr/sbin/dracut --hostonly --hostonly-cmdline --hostonly-i18n -o "plymouth dash resume ifcfg" --add nfs --mount "cfhost:/tftpboot/dumps /kdumproot//tftpboot/dumps nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.64.185,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=192.168.64.185" --include /etc/hosts /etc/hosts --include /tmp/99ip.conf -f /boot/initramfs-3.10.0-493.el7.x86_64kdump.img 3.10.0-493.el7.x86_64
Sep 20 14:44:19 opal1 kdumpctl[158175]: No permission to write to /.
Sep 20 14:44:19 opal1 dracut[160390]: No permission to write to /.
Sep 20 14:44:19 opal1 kdumpctl[158175]: mkdumprd: failed to make kdump initrd
Sep 20 14:44:19 opal1 kdumpctl[158175]: Starting kdump: [FAILED]
Sep 20 14:44:19 opal1 systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE
Sep 20 14:44:19 opal1 systemd[1]: Failed to start Crash recovery kernel arming.
Sep 20 14:44:19 opal1 systemd[1]: Unit kdump.service entered failed state.
Sep 20 14:44:19 opal1 systemd[1]: kdump.service failed.
Dracut is complaining that it can't write to /. However, it should not need to write to / it should only need to write to /boot so this message is confusing. The problem was that in the kdump.conf there was:
dracut_args --include /etc/hosts /etc/hosts --include /tmp/99ip.conf /etc/cmdline.d/01mycmdline.conf
Possibly adding a little bit of code to:
578 while (($# > 0)); do
579 if [ ${1%%=*} == "++include" ]; then
580 push include_src "$2"
581 push include_target "$3"
582 PARMS_TO_STORE+=" --include '$2' '$3'"
583 shift 2
584 fi
585 shift
586 done
That prints an error and then exists the second time through the --include loop would make the program a bit more user friendly.
1. "--include /etc/hosts /etc/hosts"
this is bogus, you should use "--install /etc/hosts" here
2. "--include /tmp/99ip.conf"
is missing the second parameter
3. ok, I will add code for multiple "--include"
Description of problem: While it is documented that --include can only be used once on a dracut command line. This fact is easy to overlook and instead of emitting a comprehensible error message mkinitrd behaves in a difficult to explain way when there are multiple --include command lines supplied. For example when I was testing something with kdump. Sep 20 14:44:18 opal1 kdumpctl[158175]: Rebuilding /boot/initramfs-3.10.0-493.el7.x86_64kdump.img Sep 20 14:44:19 opal1 dracut[160390]: Executing: /usr/sbin/dracut --hostonly --hostonly-cmdline --hostonly-i18n -o "plymouth dash resume ifcfg" --add nfs --mount "cfhost:/tftpboot/dumps /kdumproot//tftpboot/dumps nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.64.185,mountvers=3,mountport=20048,mountproto=udp,local_lock=all,addr=192.168.64.185" --include /etc/hosts /etc/hosts --include /tmp/99ip.conf -f /boot/initramfs-3.10.0-493.el7.x86_64kdump.img 3.10.0-493.el7.x86_64 Sep 20 14:44:19 opal1 kdumpctl[158175]: No permission to write to /. Sep 20 14:44:19 opal1 dracut[160390]: No permission to write to /. Sep 20 14:44:19 opal1 kdumpctl[158175]: mkdumprd: failed to make kdump initrd Sep 20 14:44:19 opal1 kdumpctl[158175]: Starting kdump: [FAILED] Sep 20 14:44:19 opal1 systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE Sep 20 14:44:19 opal1 systemd[1]: Failed to start Crash recovery kernel arming. Sep 20 14:44:19 opal1 systemd[1]: Unit kdump.service entered failed state. Sep 20 14:44:19 opal1 systemd[1]: kdump.service failed. Dracut is complaining that it can't write to /. However, it should not need to write to / it should only need to write to /boot so this message is confusing. The problem was that in the kdump.conf there was: dracut_args --include /etc/hosts /etc/hosts --include /tmp/99ip.conf /etc/cmdline.d/01mycmdline.conf Possibly adding a little bit of code to: 578 while (($# > 0)); do 579 if [ ${1%%=*} == "++include" ]; then 580 push include_src "$2" 581 push include_target "$3" 582 PARMS_TO_STORE+=" --include '$2' '$3'" 583 shift 2 584 fi 585 shift 586 done That prints an error and then exists the second time through the --include loop would make the program a bit more user friendly.