Bug 890154

Summary: remote-fs.target no longer enabled after fedup upgrade
Product: [Fedora] Fedora Reporter: Kim Bisgaard <kim-rh>
Component: systemdAssignee: systemd-maint
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: johannbg, lnykryn, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:11:07 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 Flags
systemd kernel log none

Description Kim Bisgaard 2012-12-25 11:22:02 UTC
Description of problem:
On boot does not mount NFS mounts from fstab. In my case it is impossible to login as anything but root.

How reproducible:
Allways


Actual results:
# systemctl status home.mount
home.mount - /home
          Loaded: loaded (/etc/fstab)
          Active: inactive (dead)
           Where: /home
            What: xx:/home
          CGroup: name=systemd:/system/home.mount



Expected results:
# systemctl status home.mount
home.mount - /home
          Loaded: loaded (/etc/fstab)
          Active: active (mounted) since Tue, 2012-12-25 11:59:19 CET; 19min ago
           Where: /home
            What: xx:/home
          CGroup: name=systemd:/system/home.mount


Additional info:
An F17 system FedUp'd to F18 beta.

Comment 1 Kim Bisgaard 2012-12-27 10:14:13 UTC
/etc/fstab contains:
xx:/home           /home                   nfs     defaults        0 0

# mount -va
/boot                    : already mounted
/opt                     : already mounted
/                        : ignored
/data                    : already mounted
swap                     : ignored
/dev/shm                 : already mounted
/dev/pts                 : already mounted
/sys                     : already mounted
/proc                    : already mounted
mount.nfs: timeout set for Thu Dec 27 10:54:46 2012
mount.nfs: trying text-based options 'vers=4,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xy'
/home                    : successfully mounted

Comment 2 Michal Schmidt 2013-01-07 12:14:09 UTC
Please attach a log produced by following these instructions:
http://freedesktop.org/wiki/Software/systemd/Debugging#If_You_Can_Get_a_Shell

Comment 3 Kim Bisgaard 2013-01-07 19:10:14 UTC
Created attachment 674297 [details]
systemd kernel log

Comment 4 Michal Schmidt 2013-01-08 12:43:49 UTC
It appears you don't have remote-fs.target enabled for some reason. Try:
systemctl enable remote-fs.target

Comment 5 Kim Bisgaard 2013-01-08 19:22:22 UTC
Yes that worked fine! Thanks!

The thing is - it worked fine before FedUp'ing to F18.

Comment 6 Lennart Poettering 2013-01-13 22:29:49 UTC
Hmm, our postinst scripts in systemd actually have enabled remote-fs.target explicitly since about always. Not sure what we can do about this, especially if it's not reproducible.

Comment 7 Fedora End Of Life 2013-12-21 10:04:39 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 8 Fedora End Of Life 2014-02-05 14:11:10 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.