On Tue, 2017-06-27 at 21:13 +0000, Fedora compose checker wrote:
No missing expected images.
Failed openQA tests: 6/128 (x86_64), 1/2 (arm)
New failures (same test did not fail in 26-20170625.n.0):
ID: 113830 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/113830
This is caused by bind being updated without bind-dyndb-ldap being rebuilt:
https://bugzilla.redhat.com/show_bug.cgi?id=1465187
That bug's been accepted as a blocker now, and the bind-dyndb-ldap update should be pushed stable shortly.
ID: 113908 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/113908
Just an openQA mishap (looks like clicking on the filesystem list didn't take). I've re-run the test.
ID: 113914 Test: x86_64 universal install_multi URL: https://openqa.fedoraproject.org/tests/113914
A case of https://bugzilla.redhat.com/show_bug.cgi?id=1444225 . I've re-run the test.
Old failures (same test failed in 26-20170625.n.0):
ID: 113876 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/113876
KDE doesn't seem to be notifying of available updates after install, as it should. I need to look into this in more detail.
ID: 113878 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/113878
This seems to just intermittently fail - seems like sometimes initial- setup runs and the boot works OK, sometimes it doesn't run and the boot fails as the root account is locked. Not quite sure what's going on there.
ID: 113934 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/113934
This usually fails in role decommissioning (which I just realized I still haven't reported yet), today it failed earlier due to the same bind-dyndb-ldap issue as the non-upgrade FreeIPA test.
ID: 113947 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/113947
Still https://bugzilla.redhat.com/show_bug.cgi?id=1413813 , but happily the fix for that will land very soon.