Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 5/67 (x86_64), 3/17 (i386) ID: 14899 Test: x86_64 Workstation-live-iso base_selinux URL: https://openqa.fedoraproject.org/tests/14899

ID: 14921 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/14921

ID: 14934 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/14934

ID: 14937 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/14937

ID: 14938 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/14938

ID: 14947 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/14947

ID: 14978 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/14978

ID: 14980 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/14980

On Thu, Apr 28, 2016 at 12:27:40PM -0700, Adam Williamson wrote: > On Thu, 2016-04-28 at 18:44 +0000, Fedora compose checker wrote: > > Missing expected images: > > > > Cloud_base raw-xz i386 > > Atomic raw-xz x86_64 > > > > Failed openQA tests: 5/67 (x86_64), 3/17 (i386) > > > > ID: 14899 Test: x86_64 Workstation-live-iso base_selinux > > URL: https://openqa.fedoraproject.org/tests/14899 > > Probably not worth worrying about. Actually that's a major screw up, and it affects all systems where hypervvssd, hypervfcopyd, or hypervkvpd are installed. The reason that it's only always visible that systemd cuts of the output to the console when starting getty. So depending on the ordering of things, this error will not be visible on the console, but it's still there in the logs: $ systemctl status hypervvssd ● hypervvssd.service - Hyper-V VSS daemon Loaded: loaded (/usr/lib/systemd/system/hypervvssd.service; enabled; vendor preset: enabled) Active: inactive (dead) Apr 28 16:09:35 rawhide systemd[1]: Dependency failed for Hyper-V VSS daemon. Apr 28 16:09:35 rawhide systemd[1]: hypervvssd.service: Job hypervvssd.service/start failed... $ uname -p x86_64 hypervvssd.service and friends are enabled by default in presets [https://bugzilla.redhat.com/show_bug.cgi?id=1279322], and pulled in by default in comps (in @guest-desktop-agents, which is in all desktops). > This is a weird one: systemd decided we were Hyper-V for some reason? Not really. hypervvssd.service has ConditionVirtualization=microsoft BindsTo=sys-devices-virtual-misc-vmbus\x21hv_vss.device After=sys-devices-virtual-misc-vmbus\x21hv_vss.device but Condition* is checked just before the unit is started, so a timeout occurs and a notice is logged. So everything happens according to the plan, but it's the plan that is wrong, so to speak. I filed https://bugzilla.redhat.com/show_bug.cgi?id=1331577 to start a discussion about the solution.

> > > ID: 14937 Test: x86_64 universal upgrade_2_server_64bit > > URL: https://openqa.fedoraproject.org/tests/14937 > > This is an openQA issue, the console login code breaks when KVM prints > a message about clock adjustment... I believe you'll need to play with the console= kernel cmdline argument, because virt-builder adds console=tty0 by default which makes such messages appear on current tty.

On Thu, 2016-04-28 at 12:27 -0700, Adam Williamson wrote: >   > > > > ID: 14947 Test: x86_64 universal install_mirrorlist_graphical > > URL: https://openqa.fedoraproject.org/tests/14947 > This is a concerning one, somehow anaconda managed to crash? The logs > include an anaconda coredump. The same test passed for every other > recent image, so it's some kind of transient bug, but a crash is still > a crash. I tried to generate the backtrace from the coredump and here is its part (the coredump has >200 MiB): http://paste.fedoraproject.org/360944/14619164/ I cannot really tell what happened based on the bt, though.