Project

General

Profile

Actions
Copy link

action #101295

closed

[timebox: 8h][sporadic] test fails in verify_default_target

Added by JRivrain over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Target version:
Current
Start date:
2021-10-21
Due date:
% Done:

0%

Estimated time:

Description

Observation

Sometimes, select_console fails here, we are trying to launch a command while we are still at login prompt.

openQA test in scenario sle-15-SP4-Online-ppc64le-minimal+role_minimal@ppc64le fails in
verify_default_target

Test suite description

Like default but explicitly select the system role "minimal". The resulting system should roughly correspond to an unregistered system but with access to modules for optional installation.

Reproducible

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

Expected result

Last good: 50.1 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #103791: After module failure, the console is broken size:MResolvedlivdywan2021-12-09

Actions
Actions
Copy link
 #1

Updated by maritawerner over 2 years ago

Hi Jonathan, I guess this is a ticket for the qe yast group, right? It yes, you could move it to the yast project or label it with [qe-yast] so that I do not need to triage it. Thanks a lot!

Actions
Copy link
 #2

Updated by maritawerner over 2 years ago

  • Subject changed from sporadic- test fails in verify_default_target to [qe-yast] sporadic- test fails in verify_default_target
Actions
Copy link
 #3

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: minimal+role_minimal
https://openqa.suse.de/tests/7618694

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
Actions
Copy link
 #4

Updated by oorlov over 2 years ago

  • Tags set to qe-yast-refinement
  • Project changed from openQA Tests to qe-yam
  • Subject changed from [qe-yast] sporadic- test fails in verify_default_target to sporadic- test fails in verify_default_target
  • Category deleted (Bugs in existing tests)
  • Target version set to Current
Actions
Copy link
 #5

Updated by geor over 2 years ago

Issue also appears in validate_partition_table_via_blkid (can also be seen in the verify_default_target of the same job).

The cause is the same:

  • select_console 'root-console'; runs
  • ctrl-d is pressed in the root console, forcing us back to the login prompt.
  • the script_output command (eg systemctl get-default in the case of verify_default_target module) is typed on the login prompt instead of the root console, resulting in a script timeout.

It is likely that in the first step of the script_output command, when cat - > /tmp/scriptCRKJW.sh;\n is typed, the cat command is mistyped and never started, and instead of ctrl-d being sent to end the cat part, it is sent on the root console.

A similar issue might be occurring in this yast2_nfs job (same architecture and backend) where an underlying command could be mistyped.

Actions
Copy link
 #6

Updated by jlausuch over 2 years ago

  • Related to action #103791: After module failure, the console is broken size:M added
Actions
Copy link
 #7

Updated by JERiveraMoya over 2 years ago

  • Subject changed from sporadic- test fails in verify_default_target to [timebox: 8h][sporadic] test fails in verify_default_target
  • Description updated (diff)
  • Priority changed from Normal to High
Actions
Copy link
 #8

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Rejected

It is broken console, not YaST related.
Rejecting this ticket and labeling with https://progress.opensuse.org/issues/103791

Actions
Copy link
 #9

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: yast2_nfs_v3_client
https://openqa.suse.de/tests/7923769

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
Actions
Copy link

Also available in: Atom PDF