action #81142
openVNC console corruption
Added by MDoucha over 3 years ago. Updated over 2 years ago.
0%
Description
It appears that issue #61994 is back, this time on PPC64LE. LTP tests fail to boot because switching from boot animation to login screen corrupts VNC frame buffer and needles fail to match.
https://openqa.suse.de/tests/5187741#step/boot_ltp/9
https://openqa.suse.de/tests/5187758#step/boot_ltp/8
Files
Updated by pvorel over 3 years ago
- Subject changed from VNC console corruption on PPC64LE to VNC console corruption
metan reported other broken tests on 64bit (intel and amd workers)
https://openqa.suse.de/tests/5248398#step/shutdown_ltp/52
https://openqa.suse.de/tests/5241832#step/shutdown_ltp/52
Updated by rfan1 over 3 years ago
Hi,
I hit the similar issue, https://progress.opensuse.org/issues/81808#change-360829
Updated by pvorel over 3 years ago
- Related to action #81808: [sle][security][sle15sp3] test fails in ima_appraisal_hashes about background screen chaos added
Updated by coolo over 3 years ago
- Project changed from openQA Infrastructure to openQA Project
I don't think this is an infrastructure problem - until proven differently. Do we have any test case that shows it often enough to justify any debugging on this?
Updated by MDoucha over 3 years ago
coolo wrote:
I don't think this is an infrastructure problem - until proven differently. Do we have any test case that shows it often enough to justify any debugging on this?
We have no specific test case. But we do have multiple random test failures all over OSD every day now due to this issue.
But I guess what might trigger this bug reliably would be booting to desktop and then sending alternately Ctrl+Alt+F1 and Alt+F7 with 5 second delay about a hundred times.
Updated by okurz over 3 years ago
- Target version changed from Ready to future
I don't think SUSE QE Tools can help easily here. I am convinved this needs better reproduction from test side. If you can achieve that and need help in something backend related where SUSE QE Tools can likely help we will look into this again.
Updated by vpelcak about 3 years ago
Hello.
Martin Doucha will start working on reproducer for you towards the end of the week.
Updated by szarate about 3 years ago
I wonder if it's related to: https://bugzilla.opensuse.org/show_bug.cgi?id=1160707
Updated by MDoucha about 3 years ago
szarate wrote:
I wonder if it's related to: https://bugzilla.opensuse.org/show_bug.cgi?id=1160707
Yes, it appears to be the same bug. Also reported as https://progress.opensuse.org/issues/61994 the first time it appeared a year ago on aarch64.
Updated by MDoucha about 3 years ago
- Related to action #61994: VNC console corruption on aarch64 added
Updated by MDoucha about 3 years ago
I've tried to reliably reproduce the issue by writing a test module that'll just switch between console login screen and X11 login screen and check needles after each switch but I've failed so far. When was the last time the VNC corruption happened?
Updated by acarvajal almost 3 years ago
Seen this (or something similar) three times today in SLES+HA QAM Single Incidents 15-SP3 job group:
- https://openqa.suse.de/tests/6617256#step/priority_fencing_delay/47
- https://openqa.suse.de/tests/6639074#step/priority_fencing_delay/18
- https://openqa.suse.de/tests/6617127#step/priority_fencing_delay/76
Issue seems sporadic, as test is passing with other recent MUs. Last jobs even has 3 fence/reboots and issue is present only the third time.
Updated by MDoucha almost 3 years ago
I've created PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13020 to rule out one possible cause of the console corruption. Let's see what the kernel thinks the console should look like.
Updated by MDoucha over 2 years ago
- File framebuffer-6794466.png framebuffer-6794466.png added
We have first framebuffer screenshots of the screen corruption bug (PNG version attached):
https://openqa.suse.de/tests/6794466#step/boot_ltp/4
Result: negative.
Which means that the bug is somewhere between bochsdrmfb driver and VNC client. Next, I'll try switching QEMUVGA device in kernel tests to see whether the bug shows up anyway by September.
Updated by openqa_review over 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: qam_ha_priority_fencing_node02
https://openqa.suse.de/tests/6639074
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by MDoucha over 2 years ago
I've reported kernel/QEMU bug after further investigation:
https://bugzilla.suse.com/show_bug.cgi?id=1191812