Bug ID | 1037012 |
---|---|
Summary | Service doesn't start because of unknown runlevel |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | All |
OS | Other |
Status | NEW |
Severity | Critical |
Priority | P5 - None |
Component | Basesystem |
Assignee | bnc-team-screening@forge.provo.novell.com |
Reporter | petr.m@seznam.cz |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
I upgraded my TW and I found out that "bind" doesn't start during boot. If I start it later by command "systemctl start named" service is starting without problem. A few second after boot the result of "runlevel" command is unknown. # systemctl is-enabled named named.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named Can't determine current runlevel disabled But a minute later the result of "runlevel" command is N 3. # systemctl is-enabled named named.service is not a native service, redirecting to systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named enabled