Project

General

Profile

action #115793

[tools] test fails in update_install on PowerPC size:M

Added by mgrifalconi 3 months ago. Updated 10 days ago.

Status:
Workable
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

I see very often on this test a failure at the login screen, when the test is supposed to type 'root' and find the password prompt. It's sporadic but it's painful because needs sometimes several restarts to get green

openQA test in scenario sle-15-SP2-Server-DVD-Incidents-Install-ppc64le-qam-incidentinstall@ppc64le fails in
update_install

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Incident Installation TEST
MAX_JOB_TIME=9000 due to long texlive update

Reproducible

Fails since (at least) Build :24713:libtirpc (current job)

Expected result

Last good: :25560:python-Flask-Security-Too (or more recent)

Further details

Always latest result in this scenario: latest

Acceptance criteria

  • AC1: The test does not sporadically fail anymore or the problem has been forwarded to the product maintainers

Suggestions

  • Report a product bug for ppc64le 15-SP2

Related issues

Has duplicate openQA Infrastructure - action #115820: issue with openQA typing characters on ppc64le workersRejected2022-08-26

History

#1 Updated by dzedro 3 months ago

When I opened VNC console on this failing test the VNC was not updating, whatever I wrote I didn't see the text, had to close the session and open new one then I could see the text, but again typing was not visible only after reopening the session.
Looks like some VNC bug on ppc64le 15-SP2 started to happen ~one month ago.

#2 Updated by mgrifalconi 3 months ago

  • Subject changed from [qe-core] test fails in update_install to [tools] test fails in update_install

Thanks Jozef for the investigation! Moving to the tools team then!

#3 Updated by cdywan 3 months ago

  • Has duplicate action #115820: issue with openQA typing characters on ppc64le workers added

#4 Updated by cdywan 3 months ago

  • Target version set to Ready

#5 Updated by cdywan 3 months ago

  • Subject changed from [tools] test fails in update_install to [tools] test fails in update_install size:M
  • Description updated (diff)
  • Status changed from New to Workable

#6 Updated by mkittler 2 months ago

When I opened VNC console on this failing test the VNC was not updating, whatever I wrote I didn't see the text, had to close the session and open new one then I could see the text, but again typing was not visible only after reopening the session.
Looks like some VNC bug on ppc64le 15-SP2 started to happen ~one month ago.

When also a manual VNC connection is unreliable than I'm not sure what we can do. The VNC server is provided by QEMU so maybe upgrading/downgrading the QEMU package on the worker would help (although I find it unlikely).

Is this actually specific to PowerPC?

#7 Updated by okurz 2 months ago

  • Due date set to 2022-10-21
  • Status changed from Workable to Feedback
  • Assignee set to okurz
  • Priority changed from High to Normal

Apparently the issue is not that big of a problem considering that nobody (else) answered the above questions so I assume the impact is limited. Lowering priority and picking up the ticket waiting for feedback.

#8 Updated by mgrifalconi 2 months ago

I think I only saw this on powerpc yes. Two more examples: https://openqa.suse.de/tests/9610410 https://openqa.suse.de/tests/9611313

#9 Updated by okurz 2 months ago

  • Subject changed from [tools] test fails in update_install size:M to [tools] test fails in update_install on PowerPC size:M
  • Due date deleted (2022-10-21)
  • Status changed from Feedback to Workable
  • Assignee deleted (okurz)

#10 Updated by rfan1 about 2 months ago

Add my findings:

I can see the system seems hang after booting up, and then strings we typed can't show up.

I checked several failed jobs and I can find "sysrq" messages below:
https://openqa.suse.de/tests/9611313/logfile?filename=serial0.txt


susetest login: [  280.453786] sysrq: Show State
[  280.855400] sysrq: Show Blocked State

Is it a product bug?

#11 Updated by openqa_review 30 days 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-incidentinstall
https://openqa.suse.de/tests/9832009#step/update_install/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 40 days if nothing changes in this ticket.

#12 Updated by okurz 10 days ago

  • Priority changed from Normal to High

Also available in: Atom PDF