Bug 1280103
Summary: | Failed to mount /sysroot: mount.nfs: Failed to resolve server live: Name or service not known | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Antony Messerli <antony> |
Component: | dracut | Assignee: | dracut-maint-list |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | appraprv, dracut-maint-list, harald, igeorgex, johannbg, jonathan, jsynacek, lnykryn, msekleta, s, systemd-maint, tomek, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-20 15:39:31 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: |
Description
Antony Messerli
2015-11-10 23:17:05 UTC
Moving to correct component. Another previously resolved issue that appears related for more context: https://bugzilla.redhat.com/show_bug.cgi?id=1229665 No, this was caused by a patch for systemd-fstab-generator. So, the proper solution for this is to add a systemd generator for the livenet dracut module to handle the root=live:<URL> case. Similar to: https://github.com/haraldh/dracut/commit/2c66c3bccf1ff0c3307de471a4816dbc30880b76 I made a pull request towards dracut master here: https://github.com/haraldh/dracut/pull/105 This seems to allow live booted URLs to work again. This patch uses systemd's generator arg[2] to generate an early sysroot.mount that preempts systemd-fstab-generator similiar to the dmsquash-generator. I'm not sure if that's the exact approach you're looking for but I have verified it does work and generates the early sysroot.mount for systemd. Thanks for the merge, is this something we could get backported into F23? yeah, will do, thanks! Hey Harald, has this been backported into F23 yet? Thanks! This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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' of '23'. 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 23 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. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |