action #61994
closedVNC console corruption on aarch64
0%
Description
A random problem sometimes appears on aarch64 test machines where the VM screen isn't properly cleared after boot and console output gets drawn over remnants of boot splash screen. Then the job fails because needles don't match. The problem appears less than once a week and job restart usually fixes it but it might be worth investigating further.
https://openqa.suse.de/tests/3773959#step/update_kernel/6
Files
Updated by coolo almost 5 years ago
How do you imagine we investigate this? I expect a qemu problem - and all such random qemu problems we filed, just got old in bugzilla.
Updated by okurz almost 5 years ago
- File Screenshot_20200111_110145.png Screenshot_20200111_110145.png added
- Due date set to 2020-01-21
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Current Sprint
While I agree with coolo that the fix probability is low I also think that mdoucha picked a valid approach. I prefer having actual issues reported and trying to at least handle workarounds automatically rather than repeatedly manually retriggering jobs :)
I reported https://bugzilla.opensuse.org/show_bug.cgi?id=1160707 and will create a workaround needle referencing the bug. This should be good enough to keep tests running. If the test will be closed without a fix we can replace the workaround needle with a normal needle that is forgiving enough to also accept the distorted screen as usable.
Setting to "Feedback" with due date for myself to check if the workaround needle is effective.
Created new needle "linux-login-corrupted_boot_screen-boo1160707-20200111" like this:
Updated by okurz almost 5 years ago
- Status changed from Feedback to Resolved
- Target version changed from Current Sprint to Done
The needle hasn't matched anywhere yet but is used according to https://openqa.suse.de/admin/needles . As the tests did not fail again in the same step in the original scenario I will resolve this ticket. The bug mentions a potential QEMU patch to fix corruptions though: https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg03545.html
Updated by MDoucha almost 5 years ago
- Status changed from Resolved to Feedback
- Target version changed from Done to Ready
The bug made another appearance and the workaround needle was not used. You'll need to create another needle for SLE-15+ and add "tty1-selected" tag to the old one.
https://openqa.suse.de/tests/3850002#step/boot_ltp/11
https://openqa.suse.de/tests/3849935#step/boot_ltp/6
Updated by okurz almost 5 years ago
- Status changed from Feedback to Resolved
no problem to create an updated needled: tty1-selected-corrupted_boot_screen-boo1160707-20200203
Updated by MDoucha almost 5 years ago
It looks like creating workaround needles for this issue will be a lot of work.
https://openqa.suse.de/tests/3889963#step/boot_ltp/6
Updated by okurz almost 5 years ago
Oh, I see. I didn't know that the white circles can be covered by text as well. I assumed the animation would keep a detectable picture in foreground often enough. Ok, created "linux-login-corrupted_boot_screen-boo1160707-20200217" which should be even more resilient.
Updated by MDoucha almost 5 years ago
okurz wrote:
Oh, I see. I didn't know that the white circles can be covered by text as well. I assumed the animation would keep a detectable picture in foreground often enough. Ok, created "linux-login-corrupted_boot_screen-boo1160707-20200217" which should be even more resilient.
If this is a VNC bug, there is no animation running in the background anymore when this corruption happens. Then animation ended. The console was cleared with solid black color but the VNC client didn't notice. THEN the text was printed on empty black screen but the VNC client rendered it into its dirty buffer.
Updated by MDoucha almost 4 years ago
- Related to action #81142: VNC console corruption added