Comment # 9 on bug 1093029 from Stefan Schubert

(In reply to Oliver Kurz from comment #8)
> Sorry, that does not seem to help:
Np :-)

Well from my point of view it is working now correctly:

Before the fix "reload" has been called:

2018-05-24 16:11:34 <1> susetest(24298) [Ruby] yast2/systemctl.rb:32 systemctl
reload named.service 
2018-05-24 16:11:34 <3> susetest(24298) [bash] ShellCommand.cc(shellcommand):78
named.service is not active, cannot reload.
2018-05-24 16:11:34 <1> susetest(24298) [Ruby] yast2/systemctl.rb:32 systemctl
show named.service  --property=Id  --property=MainPID  --property=Description 
--property=LoadState  --property=ActiveState  --property=SubState 
--property=UnitFileState  --property=FragmentPath 
2018-05-24 16:11:34 <1> susetest(24298) [Ruby] clients/dns-server.rb:38
DnsServer module finished

After the fix "restart" has been called:

2018-06-05 19:38:00 <1> susetest(10559) [Ruby] yast2/systemctl.rb:32 systemctl
restart named.service 
2018-06-05 19:38:00 <1> susetest(10559) [Ruby] yast2/systemctl.rb:32 systemctl
show named.service  --property=Id  --property=MainPID  --property=Description 
--property=LoadState  --property=ActiveState  --property=SubState 
--property=UnitFileState  --property=FragmentPath 
2018-06-05 19:38:00 <1> susetest(10559) [Ruby] clients/dns-server.rb:38
DnsServer module finished

Yes, it will take a while to restart the service. So I am assuming that's the
reason for your failing check script.