Project

General

Profile

Actions
Copy link

action #111093

open

[containers][sporadic][s389x] test fails in boot_to_desktop with auto_review:"The SSH Port in the SUT could not be reached within 1 minute":retry

Added by jlausuch over 2 years ago. Updated 9 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-05-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-BCI-Updates-s390x-bci_on_SLES_15-SP2_host_docker@s390x-kvm-sle12 fails in
boot_to_desktop

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build _15-SP4_10.47_minimal-image (current job)

Expected result

Last good: _15-SP4_3.9_python-3.10-image (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by jlausuch over 2 years ago

  • Priority changed from Normal to Low
Actions
Copy link
 #2

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: qam-incidentinstall-ha
https://openqa.suse.de/tests/8778353#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 28 days if nothing changes in this ticket.

Actions
Copy link
 #3

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: qam-incidentinstall
https://openqa.suse.de/tests/10244812#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.

Actions
Copy link
 #4

Updated by openqa_review 9 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: registry_2.8_on_SLES_15-SP3_podman
https://openqa.suse.de/tests/14086756#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 852 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF