Bug 2321331
| Summary: | network-legacy removed from dracut-network package | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | robin | ||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 40 | CC: | dracut-maint-list, jamacku, laszlo.gombos, lnykryn, pvalena | ||||
| Target Milestone: | --- | Keywords: | Desktop, Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-05-20 20:06:46 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
robin
2024-10-23 19:11:47 UTC
I think in that version of dracut some detection in the "meta" modules is wrong. Can you try explicitly setting NM and dbus-broker? dracut --no-kernel --modules "base network nbd network-manager dbus-broker" initramfs.img Oh, and to answer your question, we no longer support the old network scripts; we use NetworkManager instead. Thanks for the reply, the command you provided results in the following error message: dracut[E]: Module 'nbd' cannot be installed. It seems like nbd has a dependency on network-legacy specifically? https://github.com/dracut-ng/dracut-ng/blame/main/modules.d/95nbd/module-setup.sh#L22 The dependency is correct, it is set to the network meta module. Can you rerun it with the --debug option? It probably fails in the check function, and from the output it should be clearly visible why. Created attachment 2056206 [details]
dracut debug output
Output of:
sudo dracut --debug --kernel-image /mnt/boot/http/nbd/vmlinuz --modules "nbd" --compress zstd --force initrd.img > output.txt 2>&1
I cannot make sense of the debug output, so I hope someone else can.
Dracut upstream here... > dracut --no-kernel --modules "nbd" initramfs.img Workaround is to use --add instead of --modules. --modules is a footgun - see https://github.com/dracut-ng/dracut-ng/commit/eb1ae6c4f83663bfe87c835feaa649f272d780bb If you insist on using --modules there is an upstream fix - https://github.com/dracut-ng/dracut-ng/commit/c4b57722fbe65dce49105ad264dde2c2bbfc8a41 This would have been very easy to find if Fedora (at least Rawhide) would follow upstream development. Upstream has released v105 over a month ago, which is already packaged up in Arch, Gentoo, Debian, Ubuntu and even Void/Alpine/Slackware. This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 '40'. 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 40 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. Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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. |