action #119233
closed[security] boot_to_desktop test fails on specific s390 workers due to closed SSH port
100%
Description
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
Further details¶
Always latest 15-SP5 result in this scenario: latest
Note in 15-SP6 changed from s390x-kvm-sle-12-mm to s390x-kvm, and CC HDD creation has been failing.
Updated by amanzini over 2 years ago
- Status changed from New to In Progress
- Assignee set to amanzini
Updated by amanzini over 2 years 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
Updated by amanzini over 2 years ago
most probably this issue is related: https://progress.opensuse.org/issues/113528
Updated by amanzini over 2 years 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.
Updated by amanzini over 2 years ago
- Related to action #119050: [security][15sp5][s390x] test fails in boot_to_desktop added
Updated by amanzini over 2 years 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
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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz over 2 years 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.
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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by amanzini over 2 years 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
Updated by openqa_review about 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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review about 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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by openqa_review about 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: 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by tjyrinki_suse almost 2 years ago
- Status changed from Workable to Feedback
This will likely continue affecting the configuration used for testing the product in development, that is 15-SP6 later on.
Updated by tjyrinki_suse over 1 year ago
- Status changed from Feedback to Workable
No less workable than the other hard to debug s390x tickets, so changing back to Workable...
Updated by tjyrinki_suse over 1 year ago
- Subject changed from [security][15sp5][s390x] boot_to_desktop test fails on specific s390 workers to [security] boot_to_desktop test fails on specific s390 workers due to closed SSH port
- Description updated (diff)
- Start date deleted (
2022-10-24)
Added 15-SP6 "always latest" link to the description. Currently CC HDD creation has been failing, but hopefully fixed in the next build now finally.
In a related issue the switch from s390x-kvm-sle-12-mm to s390x-kvm may cause other kind of issue. Once that is observable, possibly this ticket can be closed and new ticket created to better describe the current problem.
Updated by pstivanin about 1 year ago
- Status changed from Workable to Closed
we can close this ticket since the bug is no longer present