QA (public) » openQA Project (public) » openQA Tests (public)

the "last good" https://openqa.suse.de/tests/3308767/file/vars.json shows that the DESKTOP computes to "textmode" even though the setting on the test suite is "gnome" but in the "bad" https://openqa.suse.de/tests/3343344/file/vars.json the desktop is "gnome" which apparently is not working as expected as the call to select_console 'x11' fails.

If I take a look into the git log between the "last good" and actual "first bad" https://openqa.suse.de/tests/3332878 I can find

d6bd5197a Adapt yast2 lan gui tests for new UI
1a0c81263 Optimalization of salt multimachine test
2ffafad1a (schlad/slurm_cleanup) HPC: Clean-up
9400cb483 Add retry on another exit codes due to bsc#1145521
92756bc1d autoyast: Detect profile directory
00b5aa639 Revert "set fips=1 in fips mode for the zkvm bootloader install"
23eff69d7 Wait after click to confirm selection
4718b3f3d Allow the "Tip of the day" dialog to appear after a short delay
e9462e643 in FIPS mode, add fips=1 to the kernel bootline
3bccd0778 Add bootloader test to mau-extratests-yast2ui
82cd2bf31 Replace script_run by zypper_call, query 'apache2' package only
da3266a02 Fix SLES4SAP XRDP test
2f34788a8 (rwx788/yast2_cc) Fix single import in yast2_bootloader
41e9dc640 Soften regexp for different lsblk output
36fbe124c Fix NetWeaver cluster boot issue with Gnome
d4dd27e1b Remove hacks for support server in opensuse
fca708a55 Add yast_users test module in cli mode.     - modified:   lib/main_common.pm     - new file:   tests/yast2_cmd/yast_users.pm
911007410 Public Cloud: Fix Multi-machine terraform configuration for Azure
f075ba7b7 (asmorodskyi/upload_file) serial terminal: Increase waiting time inside upload_file
c84556532 Public Cloud: add a way to create instances with UEFI parameters
700e56acb evolution_prepare_servers: upload more logs on failure
59f9dbab8 Set correct launch key for yast2_apparmor on SLE >=15
b660a368f (SeroSun/yosun/xfstests_version) xfstests: Add filesystem related info into log
a5946a240 Enable download and restore guests in prj3
8f51a14d4 Add libgcrypt test
dcdeaed93 Fix namespace support in Public Cloud tests
680d1afa0 grub_test: Handle live menu layout to boot on hard disk
c91960844 Add tuned regression test
b0051ae84 (asdil12/nice_docs) Fix relative path to css for doc in subdirs
b044d6577 Add opensuse_welcome module for live scenarios
32cea3b53 (Zaoliang/documentation-2019) Add documentation into lib/Utils/Architectures.pm
1f4ab7f39 Add Vault Namespace support in Public Cloud
8de31346b Generate docs for subdirectories
d6470fbd7 opensuse_welcome: set as a milestone
bc55808bb Enable apache installation with docs
c327d208e     btrfs-progs: update install steps         - update build setp to build all btrfs-progs utilites         - copy all binaries to /sbin         - add workaround for misc/034 test
513f8872f Add a test for NVMe IRQ spreading on NUMA
2015c2532 Fix NIC hotplugging on 12-SP2 ( bsc#959325 )
91b93f79a Allow some extra time for kubeadm shutdown
1486178b0 Add a soft-fail on SLES >12.4 when showing all profiles
531ebec36 Replace unconditional sleep with wait_screen_change based one
dcfaaacea Change conditional to include SLES >15 when installing yast2-users is needed
78a7b7437 Improve assert_and_click_until_screen_change documentation
53ba9028d (okurz/fix/memory_dump) cpanfile: Add missing dependency on 'Config::Tiny' used in lib/x11test.pm
c85d3286d Fix POD in lib/utils.pm
e28e8e8c0 Schedule supportutils.pm into migration regression check
de184d696 Check package version for sles12sp5, after upgrade
6be5a00f2 Add support for other architectures
71a38c5b9 Document how to integrate yaml schedule with yaml job group settings
04584373f Make sure welcome screen is disabled and closed
fc40bf3f6 Adjusted and enabled tests to work for QA-Maintenance.
87a5336c0 Add timeout for messages in autoyast profile
59fc75784 Add retry on zypper 105 exit on QAM tests
be19fc8ba remove redundand modukes
b2be8afac Fix shibboleth schedule
6fa1a9989 [ooffice] Close "Tip of the day" dialog in desktopapps-documentation-x11
d6cc92bc5 Tolerate different number of significant digits in fdisk output
60b3817fd Use $console var consistently in unlock_zvm_disk()
ac49a9e71 Re-enable VNC for s390x
adc43d071 Revert "evolution_prepare_servers: use 'consoletest' as base to upload logs on failure"
c98b8b14d Document methods in lib/opensusebasetest.pm
637ac8f04 Don't use hardcoded user bernhard
7b11a445c system_workarounds: do not run on LIVE_INSTALLATION
19b27d1b9 Solve nfs-server rpcbind.socket conflict
493845aa3 Solve nfs-server rpcbind conflict
5b6674d24 Solve nfs-server check conflict
157fb43b5 Add rpcbind service check
37de4ab9e Use vendor-specific serial console for offline upgrade
03e28c731 Enable yast2-bootloader in y2uitest_gui extratest

I am pretty sure that ac49a9e71 , that is https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8306 , is at fault for the regression but the commit looks legit so I suggest you crosscheck what you expect from "migration" point of view and adapt the test accordingly.

1)I try to do manual check from 12sp4->15sp1, but find an issue on 12sp4, vncmanager seems not work on 12sp4 and i have submitted an issue https://bugzilla.suse.com/show_bug.cgi?id=1151009.
I have no idea for 390 12sp4 is there any specific vnc configuration needed?

2)Another question is, for dev mode for debug s390 in openqa, how to correctly using vnc client/ssh access it?

coolgw wrote:

1)I try to do manual check from 12sp4->15sp1, but find an issue on 12sp4, vncmanager seems not work on 12sp4 and i have submitted an issue https://bugzilla.suse.com/show_bug.cgi?id=1151009.
I have no idea for 390 12sp4 is there any specific vnc configuration needed?

2)Another question is, for dev mode for debug s390 in openqa, how to correctly using vnc client/ssh access it?

I fear it's not easily possible to connect to the System under Test - I suggest to follow the comment from oliver

Base following test run, i suspect this is an xvnc configure issue or product bug on 15gm
https://openqa.suse.de/tests/3380630#step/online_migration_setup/20

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

This bug is still referenced in a failing openQA test: autoupgrade_sles12sp5_scc_asmm+lgm_all_full
https://openqa.suse.de/tests/3450190

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"
3. The label in the openQA scenario is removed

Some detailed reason for this problem, one is for SuSEfirewall2 and another is for GDM.

https://bugzilla.suse.com/show_bug.cgi?id=1154153

https://bugzilla.suse.com/show_bug.cgi?id=1154156

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

This bug is still referenced in a failing openQA test: skip_registration+workaround_modules
https://openqa.suse.de/tests/3527049

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"
3. The label in the openQA scenario is removed

okurz wrote:

The latest two jobs in this scenario and one in between incomplete rather than end up failed, e.g. see https://openqa.suse.de/tests/3576498#next_previous . This also prevents the carry over to work and should be avoided where possible. Please take care to prevent the incomplete, e.g. turn it into a consistent "fail" or – probably even better – detect the product bug situation and apply a workaround with soft-fail. Please make sure to handle incompletes with urgency so that we can react in a reasonable manner to backend regressions, product bugs or test issues.

incomplete case show following info instead of "connection timeout" error(normal failed case), need further check
[2019-11-09T19:35:30.271 CET] [debug] Backend process died, backend errors are reported below in the following lines:
Bizarre copy of ARRAY in list assignment at /usr/lib/perl5/vendor_perl/5.26.1/Devel/StackTrace.pm line 61.Bizarre copy of ARRAY in list assignment at /usr/lib/perl5/vendor_perl/5.26.1/Devel/StackTrace.pm line 61. <==== !!!!!!!!!!!!

Try to rerun it and seems not happen again, you can check result of https://openqa.suse.de/tests/3576498#next_previous.

@okurz: do you have any idea why Backend process died with "Bizarre copy of ARRAY in list assignment at /usr/lib/perl5/vendor_perl/5.26.1/Devel/StackTrace.pm" ?

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles11sp4_to_developing_kvm
https://openqa.suse.de/tests/5188035

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"
3. The label in the openQA scenario is removed

if you check following case, backend also crash after select_console x11
https://openqa.suse.de/tests/5217811#next_previous

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

This bug is still referenced in a failing openQA test: offline_sles12sp3_ltss_media_sdk-asmm-contm-lgm-tcm-wsm_all_full
https://openqa.suse.de/tests/5671296

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"
3. The label in the openQA scenario is removed

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

This bug is still referenced in a failing openQA test: offline_sles12sp3_ltss_media_sdk-asmm-contm-lgm-tcm-wsm_all_full
https://openqa.suse.de/tests/5671296

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"
3. The label in the openQA scenario is removed

Verify to add reset_consoles before select_console(x11), wait https://openqa.nue.suse.com/tests/5754981#step/check_upgraded_service/261

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

This bug is still referenced in a failing openQA test: online_sles15sp1_ltss_pscc_basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/5976469

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"
3. The label in the openQA scenario is removed

check latest result, current error happen on await install module, issue happen after ~1000s during installation phase, normally the await install will finished after ~30min=1800s , so vnc connection start trigger some error during installation phase, either vnc server side(vnc server in s390) or vnc client(openqa script)
https://openqa.suse.de/tests/5927178#downloads

Issue happen during install phase, if we need exclude product vnc issue we need find way to get out /var/log/YaST2/vncserver.log when issue happen, BUT when this issue happen, openqa already report error and exit.

================issue happen during installation============
Initializing virtual console...

Found an xterm terminal on /dev/console (135 columns x 27 lines).
Sampling every 5 s to /var/log/YaST2/memsample.zcat

starting VNC server...
A log file will be written to: /var/log/YaST2/vncserver.log ...

*** You can connect to , display :1 now with vncviewer
*** Or use a Java capable browser on http://:5801/

(When YaST2 is finished, close your VNC viewer and return to this window.)

Active interfaces:

eth0: 52:54:00:ab:3f:21
10.161.145.19/20
fe80::5054:ff:feab:3f21/64

*** Starting YaST2 ***
================issue happen during installation============

Reproduced the same issue on consoletest_finish. https://openqa.nue.suse.com/tests/6158370

leli wrote:

Reproduced the same issue on consoletest_finish. https://openqa.nue.suse.com/tests/6158370

In job 6158370 the openqa crash and you can not get any vnc related log, so no idea what's happen next, we can check with software the error happen before openqa crash related or not.

compare with the good one(https://openqa.nue.suse.com/tests/6164495/file/autoinst-log.txt) you can find openqa catch the error but it still can continue (!!! consoles::VNC::catch {...}), also new vnc opened after catch the error.

[2021-06-03T07:20:23.123 CEST] [debug] <<< backend::console_proxy::ANON(wrapped_call={
"args" => [],
"function" => "reset",
"wantarray" => undef,
"console" => "user-console"
})
[2021-06-03T07:20:23.342 CEST] [debug] tests/console/consoletest_finish.pm:51 called testapi::wait_still_screen
[2021-06-03T07:20:23.342 CEST] [debug] <<< testapi::wait_still_screen(timeout=30, stilltime=2, similarity_level=47)
[2021-06-03T07:20:25.857 CEST] [debug] >>> testapi::wait_still_screen: detected same image for 2 seconds, last detected similarity is 1000000
[2021-06-03T07:20:25.967 CEST] [debug] tests/console/consoletest_finish.pm:56 called testapi::select_console
[2021-06-03T07:20:25.967 CEST] [debug] <<< testapi::select_console(testapi_console="x11", await_console=0)
[2021-06-03T07:20:25.969 CEST] [warn] !!! consoles::VNC::catch {...} : Error in VNC protocol - relogin: unexpected end of data <====
[2021-06-03T07:20:26.112 CEST] [debug] tests/console/consoletest_finish.pm:57 called x11utils::ensure_unlocked_desktop -> lib/x11utils.pm:80 called testapi::assert_screen
[ 3272.024231] systemd[1]: /usr/lib/systemd/system/xvnc@.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[ 3272.027166] systemd[1]: Started Xvnc Server (10.162.6.237:46406). <====
[ 3272.038129] Xvnc[17154]: vncext: VNC extension running! <====
[ 3272.038491] Xvnc[17154]: vncext: created VNC server for screen 0
[ 3272.039083] Xvnc2021-06-03T01:20:25.988404-04:00 susetest Xvnc[17154]: Connections: accepted: [::ffff:10.162.6.237]::46406
[17154]: Connections: accepted: [::ffff:10.162.6.237]::46406
[ 3272.039444] Xvnc[17154]: vncext: added inetd sock
[ 3272.152628] Xvnc[17154]: SConnection: Client needs protocol version 3.8
[ 3272.153515] Xvnc[17154]: SConnection: Client requests security type None(1)
[ 3272.155822] Xvnc[17154]: VNCSConnST: Server default pixel format depth 24 (32bpp) big-endian rgb888
[ 3272.156875] Xvnc[17154]: VNCSConnST: Client pixel format depth 24 (32bpp) big-endian rgb888

I expect feedback on fix following ticket and we can get more detail error info.
#77314 Test incompletes with "(Bizarre copy of (HASH|ARRAY) in list assignment|attempt to copy freed scalar)", improve error feedback.

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

This bug is still referenced in a failing openQA test: online_sles15sp1_rmt_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6592688

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 label in the openQA scenario is removed

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles12sp5_to_developing_kvm@64bit-ipmi
https://openqa.suse.de/tests/6616935

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 label in the openQA scenario is removed

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

This bug is still referenced in a failing openQA test: online_sles15sp2_scc_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6915980

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 label in the openQA scenario is removed

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

This bug is still referenced in a failing openQA test: online_sles15sp2_scc_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6915980

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 label in the openQA scenario is removed

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

This bug is still referenced in a failing openQA test: online_sles15sp2_scc_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6915980

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

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

This bug is still referenced in a failing openQA test: online_sles15sp2_scc_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6915980

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

Move to backlog, we can move it back when needed.

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

This bug is still referenced in a failing openQA test: online_sles15sp2_scc_basesys-srv_def_full_zypp
https://openqa.suse.de/tests/6915980

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

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles12sp5_to_developing_kvm
https://openqa.suse.de/tests/7915588

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

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

This bug is still referenced in a failing openQA test: prj2_host_upgrade_sles12sp5_to_developing_kvm
https://openqa.suse.de/tests/7929071

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

These tickets are not on high prio

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.