![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1036630
http://bugzilla.opensuse.org/show_bug.cgi?id=1036630#c9
Dominique Leuenberger
Looks like this has nothing to do with my changes, because the latest version with the openssl fix is working fine for me:
*** This bug has been marked as a duplicate of bug 1040027 ***
I agree - this is no DUP; when this bug here started, it was claimed to be an issue due to the missing /etc/rc.d symlink *which was boo#1035062); for one snapshot there was boo#1040027 an issue (chrooted startup failed due to openssl - but that was actually blocked by openQA) The fact that yast2_bind still fails despite the reported underlying bugs being fixed indicates that really somebody has to look at the yast module itself (again) Last test run with failure: https://openqa.opensuse.org/tests/410643#step/yast2_dns_server/9 -- You are receiving this mail because: You are on the CC list for the bug.