Bug 1037012 - Service doesn't start because of unknown runlevel
Summary: Service doesn't start because of unknown runlevel
Status: RESOLVED DUPLICATE of bug 1035062
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: All Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-01 14:05 UTC by Petr Matula
Modified: 2017-07-31 13:39 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Matula 2017-05-01 14:05:38 UTC 
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
Comment 2 Franck Bui 2017-07-31 13:39:35 UTC 
Probably was a duplicate indeed.

Let's close it as such.

Feel free to re-open if that's not the case.

*** This bug has been marked as a duplicate of bug 1035062 ***