Project

General

Profile

Actions
Copy link

action #43529

closed

[sle][functional][u] test fails in system_prepare - password-prompt matched too late, probably timeout issue

Added by zluo over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
High
Assignee:
mgriessmeier
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 21
Start date:
2018-11-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Compared with last successful test run, I can see that it failed before password-prompt just matched after it.

Observation

openQA test in scenario sle-12-SP4-Server-DVD-s390x-minimal+base@s390x-kvm-sle12 fails in
system_prepare

Reproducible

Fails since (at least) Build 0455 (current job)

Expected result

Last good: 0455 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 5 years ago

  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Target version set to Milestone 20

should be easy to just wait longer here

Actions
Copy link
 #2

Updated by jorauch over 5 years ago

  • Subject changed from [sle][functional][u] test fails in system_prepare - password-prompt matched too late, properly timeout issue to [sle][functional][u] test fails in system_prepare - password-prompt matched too late, probably timeout issue
  • Assignee set to jorauch

Taking a look

Actions
Copy link
 #3

Updated by jorauch over 5 years ago

Looks to me like the mentioned password prompt belongs to the post-fail hook and the connection before took too long (since we can see the cursor I am pretty sure we're not seeing the LPAR)
Might again be activate_console

Actions
Copy link
 #4

Updated by jorauch over 5 years ago

  • Status changed from Workable to Feedback
  • Assignee deleted (jorauch)

As discussed with mgriessmeier:
will set this to feedback since it looks like a one time failure so far and has not been seen anywhere else
If this does no appear again in a reasonable timeframe (lets say 1 month) we should close it

Actions
Copy link
 #5

Updated by mgriessmeier over 5 years ago

  • Assignee set to mgriessmeier
Actions
Copy link
 #6

Updated by okurz over 5 years ago

  • Target version changed from Milestone 20 to Milestone 21
Actions
Copy link
 #7

Updated by mgriessmeier over 5 years ago

  • Status changed from Feedback to Rejected

not relevant anymore, reopen if reoccurs in SP5

Actions
Copy link
 #8

Updated by okurz over 5 years ago

Why should it not be relevant anymore? I guess looking at the "SLE12SP4" test results within the last month that is fooling us as there was just one single build within that timeframe, the GM build.

Actions
Copy link

Also available in: Atom PDF