Bug ID | 963971 |
---|---|
Summary | remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | 2015* |
Hardware | x86-64 |
OS | Other |
Status | NEW |
Severity | Major |
Priority | P5 - None |
Component | Basesystem |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | manfred.h@gmx.net |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Since quite some time I see varying messages about systemd having issues with remote file systems vs. nfs related services vs. name resolution services. Sometimes my NFS(4) server doesn't even start. Here is an example on the latest TW version "openSUSE Tumbleweed (20160126) (x86_64)": # journalctl | grep deleted Jan 28 12:17:05 saturn systemd[1]: remote-fs-pre.target: Job remote-fs-pre.target/start delete to break ordering cycle starting with remote-fs.target/start On some other systems I see have this: nss-lookup.target: Job nss-lookup.target/start deleted to break ordering cycle starting with rpc-statd.service/start rpc-statd.service: Job rpc-statd.service/start deleted to break ordering cycle starting with nfs-server.service/start As this is not predictable and may lead to some important services not being started, I rate this rather important.