Bug 1037012

Summary:	Service doesn't start because of unknown runlevel
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Petr Matula <petr.m>
Component:	Basesystem	Assignee:	systemd maintainers <systemd-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	fbui
Version:	Current
Target Milestone:	---
Hardware:	All
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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 1 Petr Matula 2017-05-02 12:02:04 UTC

https://forums.opensuse.org/showthread.php/524544-LSB-Units-Skipped-on-Boot?highlight=named

https://bugzilla.suse.com/show_bug.cgi?id=1035062

Probably the same problem

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 ***