Bug 1291045
Summary: | NFS mount in fstab fails on boot (NM shows 'startup complete' before device activation). | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Hubick <chris> | ||||
Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> | ||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 23 | CC: | dcbw, lkundrak, psimerda | ||||
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 16:58:42 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: | |||||||
Attachments: |
|
Description
Chris Hubick
2015-12-13 04:50:37 UTC
Sorry, the last potential duplicate should have been Bug 1062704. Adding the fstab option 'comment=systemd.mount' didn't fix this for me, but then also adding '_netdev' did.
> [root@CHWorkstation ~]# cat /etc/fstab | grep chnas
> chnas.chd.hubick.com:/mnt/chpool/chdata /home/hubick/chd/chdata nfs defaults,hard,sync,nosuid,_netdev,comment=systemd.mount 0 0
I can understand 'comment=systemd.automount', but shouldn't 'comment=systemd.mount' be the default for fstab entries? And isn't '_netdev' a safe assumption for NFS mounts? i.e. Shouldn't this all have Just Worked?
(In reply to Chris Hubick from comment #2) > Adding the fstab option 'comment=systemd.mount' didn't fix this for me, but > then also adding '_netdev' did. I lied. It made it work once in a while, but still less than half the time. Some kind of race condition then I'm guessing :-( 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. |