Comment # 4 on bug 1093029 from Stefan Schubert

(In reply to Oliver Kurz from comment #3)
> openQA did this job for us :) The latest result show a failure again:
> https://openqa.opensuse.org/tests/682121

Good point :-)

> 
> As stated in the description: It's a sporadic issue. I assume the problem
> can not be reproduced manually by simply looking for the service to be
> running after some seconds. I assume when you want to check *manually* then
> you need to call "yast2 dns_server; systemctl is-active named" so that the
> systemctl call is immediately executed after exiting the yast2 module.
Ah, ok. I have seen this too sometime ago. The server has been in state
"starting" in that case. Hopefully this works:
https://github.com/yast/yast-dns-server/pull/68