Project

General

Profile

action #108305

[sle][migration][sle15sp4][Other]test fails in reconnect_mgmt_console - suspect firewall related issue on vnc

Added by coolgw 3 months ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-03-15
Due date:
% Done:

0%

Estimated time:
4.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Continuous-Migration-SLE15SP4-s390x-offline_sles15ga_sles15sp2_sles15sp4_media_all_full_s390x_ph0@s390x-kvm-sle15 fails in
reconnect_mgmt_console

Test suite description

offline SLES15GA -> SLES15SP2 -> SLES15SP4 s390x

Reproducible

Fails since (at least) Build 101.1

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by coolgw 3 months ago

  • Status changed from New to In Progress

#2 Updated by coolgw 3 months ago

first run failed on patch_sle, rerun:
https://openqa.suse.de/tests/8333841#

#3 Updated by coolgw 3 months ago

kick out issue 1197167

#4 Updated by leli 3 months ago

  • Estimated time set to 10.00 h

#5 Updated by okurz 3 months ago

So that you don't leak API key+secret again I recommend you put your API key and secret into a config file, see the output of openqa-cli --help for help.

#6 Updated by coolgw 3 months ago

okurz wrote:

So that you don't leak API key+secret again I recommend you put your API key and secret into a config file, see the output of openqa-cli --help for help.

Thanks a lot : ) Will keep in mind

#7 Updated by coolgw 3 months ago

  • Status changed from In Progress to Resolved
  • Estimated time changed from 10.00 h to 4.00 h

#8 Updated by openqa_review 2 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: offline_sles15ga_sles15sp2_sles15sp4_media_all_full_
https://openqa.suse.de/tests/8551584#step/reconnect_mgmt_console/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.

#9 Updated by coolgw 2 months ago

  • Status changed from Resolved to In Progress

try to workaround issue on openqa, since issue still no one take care.

#10 Updated by coolgw 2 months ago

/usr/share/openqa/script/client --host openqa.suse.de isos post REPO=SLE-15-SP4-Online-s390x-Build129.1-Media1 ARCH=s390x BUILD=129.1 \ BUILD_SLE=129.1 BUILD_HA=129.1 BUILD_SDK=129.1 BUILD_SES=129.1 BUILD_SLE=129.1 VERSION=15-SP4 DISTRI=SLE FLAVOR=Continuous-Migration-SLE15SP4 \

CASEDIR=https://github.com/coolgw/os-autoinst-distri-opensuse.git#0424 \
TEST=offline_sles15ga_sles15sp2_sles15sp4_media_all_full_s390x_ph0,online_sles15ga_sles15sp2_sles15sp4_pscc_all_full_y_s390x_ph1
WARNING: openqa-client is deprecated and planned to be removed in the future. Please use openqa-cli instead

{
count => 2,
failed => [],
ids => [8625367, 8625368],
scheduled_product_id => 906363,
}
You have new mail in /var/spool/mail/root

#11 Updated by openqa_review about 2 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: offline_sles12sp4_ltss_pscc_sdk-asmm-contm-lgm-tcm-wsm-pcm_all_full_x11
https://openqa.suse.de/tests/8636826#step/check_upgraded_service/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.

Also available in: Atom PDF