Project

General

Profile

action #119233

[security][15sp5][s390x] boot_to_desktop test fails on specific s390 workers

Added by pstivanin 5 months ago. Updated 1 day ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-10-24
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
fail

Description

Observation

Test fails because SSH port is closed.

https://openqa.suse.de/tests/9777034#step/boot_to_desktop/16
https://openqa.suse.de/tests/9777032#step/boot_to_desktop/16

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Related issues

Related to openQA Tests - action #119050: [security][15sp5][s390x] test fails in boot_to_desktopRejected2022-10-19

Related to openQA Tests - action #113528: [qe-core] test fails in bootloader_zkvm - performance degradation in the s390 network is causing serial console to be unreliable (and killing jobs slowly)Resolved2022-07-132022-07-18

Related to openQA Infrastructure - action #123960: s390x tests fail to log into VNC console on worker2 due to already present VM with same mac addressResolved2023-02-06

History

#1 Updated by amanzini 5 months ago

  • Status changed from New to In Progress
  • Assignee set to amanzini

#2 Updated by amanzini 5 months ago

after some investigation, same test passes forcing worker class to s390-kvm-sle12 (without -mm). So probably it is related to worker infrastructure
https://openqa.suse.de/tests/9808915

#3 Updated by amanzini 5 months ago

most probably this issue is related: https://progress.opensuse.org/issues/113528

#4 Updated by amanzini 5 months ago

  • Subject changed from [security][15sp5][s390x] test fails in cc_audit_remote and cc_net_case to [15sp5][s390x] boot_to_desktop test fails on specific s390 workers
  • Status changed from In Progress to Workable
  • Assignee deleted (amanzini)

If you take as example https://openqa.suse.de/tests/9758227#dependencies you can see that when the test is scheduled on ' grenache* ' , the console is behaving in a weird way.
Basically sometimes the system stays still in a black screen with a blinking cursor and does not prompt for the password, so the needle fails to match.

There is a related ticket but it is closed. According to network performance metrics, ping response seems good.

#5 Updated by amanzini 5 months ago

  • Related to action #119050: [security][15sp5][s390x] test fails in boot_to_desktop added

#6 Updated by amanzini 5 months ago

  • Related to action #113528: [qe-core] test fails in bootloader_zkvm - performance degradation in the s390 network is causing serial console to be unreliable (and killing jobs slowly) added

#7 Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/9881884#step/boot_to_desktop/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 28 days if nothing changes in this ticket.

#8 Updated by okurz 4 months ago

  • Subject changed from [15sp5][s390x] boot_to_desktop test fails on specific s390 workers to [security][15sp5][s390x] boot_to_desktop test fails on specific s390 workers

amanzini please do not remove the team assignment keyword in the subject line. If another QE squad should take over then the according keyword should be added or the ticket moved to a subproject but we should not have tickets without team assignment.

#9 Updated by openqa_review 4 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/10028917#step/boot_to_desktop/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 28 days if nothing changes in this ticket.

#10 Updated by openqa_review 3 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/10219181#step/boot_to_desktop/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 56 days if nothing changes in this ticket.

#11 Updated by amanzini about 1 month ago

  • Related to action #123960: s390x tests fail to log into VNC console on worker2 due to already present VM with same mac address added

#12 Updated by openqa_review about 1 month ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/10375310#step/boot_to_desktop/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 28 days if nothing changes in this ticket.

#13 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: cc_audit_remote_server@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/10532936#step/boot_to_desktop/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 28 days if nothing changes in this ticket.

#14 Updated by openqa_review 1 day ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cc_audit_remote_client@s390x-kvm-sle12-mm
https://openqa.suse.de/tests/10603882#step/boot_to_desktop/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 56 days if nothing changes in this ticket.

Also available in: Atom PDF