Bugzilla – Bug 1143051
[Build 20190723] openQA test fails in firstrun - system doesn't boot up anymore
Last modified: 2019-12-19 14:18:00 UTC
please my ticket as well. I checked this issue on o3:
100 test runs on O3:
We can see a lot of test runs just failed.
Normal the rebooting just take about 20 seconds, we have set timeout for 1000.
But I don't think this is timeout issue.
Logs can be found at: https://openqa.opensuse.org/tests/989200#downloads
Unfortunately post_fail_hook doesn't work in this case so there is no logs than openqa logs available.
openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
## Test suite description
Same as jeos, plus some more tests.
Fails since (at least) Build (https://openqa.opensuse.org/tests/877894)
## Expected result
Last good: (unknown) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=JeOS-for-kvm-and-xen&machine=64bit_virtio-2G&test=jeos-extra&version=Tumbleweed)
I think firstrun is handled by the jeos folks so let's reassign this old bug accordingly.
(In reply to Franck Bui from comment #1)
> I think firstrun is handled by the jeos folks so let's reassign this old bug
I debugged this a while ago and it was caused by systemd losing state during daemon-reloads triggered by btrfsmaintenance startup, so likely a dup of bug 1137373.
It's not reproducible for several months now, so let's close it as WORKSFORME.