Hello,
As of Tumbleweed 20170424, I’ve noticed these services -all LSB- never start at boot:
named.service
vmware.service
vmware-USBArbitrator.service
vmware-workstation-server.service
I tried to enable them through systemctl enable <service> and /usr/lib/systemd/systemd-sysv-install enable <service> with no error but no effect either.
Greetings,
Benjamin Diaz
PSE@Novell de Mexico
Apparently build issue - wrong path to /etc/init.d/rc?.d:
3500 execve("/usr/lib/systemd/system-generators/systemd-sysv-generator", "/usr/lib/systemd/system-generato"..., "/tmp/normal", "/tmp/early", "/tmp/late"], /* 85 vars */]) = 0
...
3500 lstat("/etc", {st_mode=S_IFDIR|0755, st_size=4852, ...}) = 0
3500 lstat("/etc/rc.d", 0x7ffef56f5320) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/boot.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/rc1.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/rc2.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/rc3.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/rc4.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
3500 open("/etc/rc.d/rc5.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
So no WantedBy links are created for run-level targets. I’m surprised it happened just now - there was no changes to generator recently according to changelog. May be /etc/rc.d compatibility link was present in the past, cannot say.
OK, /etc/rc.d link was provided by filesystem package. Last changelog is about /etc/init.d tree moved to insserv-compat. So I guess we need bug report against insserv-compat which should provide compatibility link /etc/rc.d -> /etc/init.d as we plausibly have other programs relying on it.
Workaround is obviously to create link manually.
I submitted SR for insserv-compat that should fix this issue.
Issue resolved? Is it currently safe to update TW? Or should I wait another week? 
Fixed as of 2070510, without the workaround mentioned above.
Thanks for the help,
Benjamin Diaz