Bug 2136062
| Summary: | hostonly="no" don't add mdadm.conf | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Harald Reindl <h.reindl> |
| Component: | dracut | Assignee: | dracut-maint-list |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | dracut-maint-list, jamacku, jonathan, laszlo.gombos, lnykryn, pvalena |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-25 15:56:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. This is expected. Not a bug - see https://github.com/dracutdevs/dracut/blob/master/modules.d/90mdraid/module-setup.sh#L100 non-hostly by default is not expected to pick up host specific configuration files. If you know what you want you can add files on the dracut command line. I suggest to close this bug or perhaps suggest how can the dracut project improve documentation to explain this better. it is NOT expected - BEFORE hostonly became the default all my machines had md01/md1 and not md127/md128 and the point where you siwtch to nion-hostonly is before you move your disks to a new machine BTW: i found that file on one of two machines hundrets of kilometers away installed 2012 which SUDDENLY switched years ago from md0/md1 to md127/md128 [root@srv-rhsoft:~]$ cat /etc/dracut.conf.d/92-mdadm.conf mdadmconf="yes" Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |
recently i migrated systems with rootfs on RAID10 to RAID1 and for safety reasons i switched to hostonly="no" and executed "dracut -f" to have the new mdadm.conf with the new RAID-UUIDs in the initrd before reboot to a live-cd for the dd-sync of the RAID contents what should i say: the initrd didn't contain "mdadm.conf" and "lsinitrd" confirmed that after hours to get the system started at all again i switched back to hostly=yes, "dracut -f", voila "lsinitrd" confirmed "mdadm.conf" is there again and after a reboot my arrays where called md0/md1 instead of "md126/md127" i can see no logic here given that a non-hostonly initrd is desired when you switch hardware and also i don't understand how it's decided at all when the initrd contains mdadm on a test-vm with a RAID not containing system/boot it's not there in any case [root@testserver:~]$ lsinitrd | grep mdadm [root@testserver:~]$ cat /proc/mdstat Personalities : [raid10] md0 : active raid10 sdf1[5] sde1[4] sdd[7] sdc[6] 2072576 blocks super 1.2 256K chunks 2 near-copies [4/4] [UUUU]