action #14950
closedleftover fragments/artifacts on the console in many different test scenarios
0%
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-s390x-minimal+base@zkvm fails in
consoletest_setup
Reproducible¶
Fails since (at least) Build 0058
Expected result¶
Last good: 0057 (or more recent)
Problem¶
H1. Upgrade to Leap 42.2 introduced some broken qemu and/or vnc introducing artifacts
Further details¶
Always latest result in this scenario: latest
Originally spotted only on openqaworker5, now also on others.
Updated by zluo about 8 years ago
Updated by okurz about 8 years ago
- Subject changed from leftover fragments on the console (so far only spotted on openqaworker5 to zkvm: leftover fragments on the console
- Description updated (diff)
- Priority changed from Normal to High
s390x minimal+base on openqaworker2 shows the same issue so not only openqaworker5
Updated by mgriessmeier about 8 years ago
probably because we updated all of the workers in the meantime - before only openqaworker5 was Leap 42.2
Updated by okurz about 8 years ago
- Related to action #15410: susedistribution::ensure_installed: if pkcon fails, screenlock might hide error added
Updated by okurz about 8 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
- Subject changed from zkvm: leftover fragments on the console to leftover fragments/artifacts on the console in many different test scenarios
- Description updated (diff)
- Category changed from Bugs in existing tests to 132
https://openqa.opensuse.org/tests/318252#step/install_and_reboot/16 is pretty convincing on me. Looking at the video https://openqa.opensuse.org/tests/318252/file/video.ogv shows that at some time the screen does not update anymore and then slowly fills up with black artifacts. But the test still continues because the SUT reboots, see https://openqa.opensuse.org/tests/318252#step/install_and_reboot/17
Updated by szarate about 8 years ago
For both tests mentioned in this ticket, there's at least one occurence of considering VNC stalled - turning black which might cause somehow the console to misbehave and not clear correctly the screen...
Updated by okurz about 8 years ago
#14950#note-5 is not the same issue as it seems but rather #14570 instead. I will comment there.
Anyway, as it seems on a current Leap 42.2 machine running a qemu instance and standard "vncviewer" also shows artifacts so it really looks like some issues with vnc on our hosts.
Updated by okurz about 8 years ago
- Related to action #14570: textmode installations can get destorted (black artifacts on screen) added
Updated by okurz about 8 years ago
- Assignee set to mgriessmeier
mgriessmeier, did you report a bug about this already? If not, as you stated you have seen this more often, please gather the data for a bug report on what you think might be influencing this, e.g. package versions on the worker OS for Xvnc, vncviewer, qemu, etc.
Updated by mgriessmeier about 8 years ago
no I didn't - actually I didn't see this occur for a while now
Updated by okurz about 8 years ago
- Status changed from New to Resolved
As it is also not mentioned on https://w3.nue.suse.com/~okurz/openqa_suse_de_status.html assumed to be fixed, maybe by any package update on the worker hosts