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

this module just called select_root_console, but the tty was not showing at that time. And the desktop was not ready at that time, maybe the desktop was crash at that time, which we need to dig in.

Now this case was moved to s390x and passed.
https://openqa.suse.de/tests/3473156

snapper_rollback
failed https://openqa.suse.de/tests/3554809
fixed https://openqa.suse.de/tests/3570051

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8881

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

This bug is still referenced in a failing openQA test: offline_sles15_media_basesys-srv-lgm-pcm_def_full
https://openqa.suse.de/tests/3598328

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

I checked the latest referenced failure https://openqa.suse.de/tests/3627740#step/patch_sle/105 and what I see there is that the check after switch to tty6 times out after 60s. Did you check if maybe the X server itself runs on tty6, 60s should be well enough to switch to the display but you can also change the timeout or scale it with SCALE_TIMEOUT for checking.

For https://openqa.suse.de/tests/3627740#step/patch_sle/105, we can't verify it now cause the 93.1 iso file was deleted. I'll close that PR to use SCALE_TIMEOUT for this kind of issue.

Please do not use "TIMEOUT_SCALE" for production tests, only for debugging or crosschecking or in case of really slow machines which we do not use in production.

If you check the success verification log you will find switch console action complete within one second, means osd env recover by itself after rerun, not related with
PR(https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8881) which enlarge the timeout.
I guess two situation can trigger this issue
1) Something wrong within linux(crash happen? X-windows freeze?)
2) The ctl+Fx key from os-autoinst lost

Currently my proposal for this issue are:
1) Submit an PR for collect more log (means we should open more debug msg and upload more log)
2) Try send ctl+Fx key more times, to see situation become good or not

another one: https://openqa.suse.de/tests/3696886#step/orphaned_packages_check/3

the call path is like:
activate_console ->my @tags = ("tty$nr-selected", "text-logged-in-$user");
[2019-12-23T08:31:09.800 CET] [debug] MMM -> patch_sle:wait_boot
[2019-12-23T08:31:09.800 CET] [debug] MMM -> opensusebasetest:wait_boot
[2019-12-23T08:31:23.730 CET] [debug] MMM ->opensusebasetest:wait_boot_past_bootloader
[2019-12-23T08:32:16.643 CET] [debug] MMM -> into the desktop
[2019-12-23T09:50:09.566 CET] [debug] MMMM ->activate_console
[2019-12-23T09:50:09.566 CET] [debug] activate_console, console: root-console, type: console
[2019-12-23T09:50:09.566 CET] [debug] MMM ->NNNNN call self->hyperv_console_switch(root-console, 6)
[2019-12-23T09:50:09.566 CET] [debug] MMM ->hyperv_console_switch
[2019-12-23T09:50:09.566 CET] [debug] /var/lib/openqa/share/tests/sle/tests/update/patch_sle.pm:75 called migration::setup_sle
[2019-12-23T09:50:09.566 CET] [debug] <<< testapi::wait_still_screen(similarity_level=47, stilltime=5, timeout=30)
[2019-12-23T09:50:15.097 CET] [debug] >>> testapi::wait_still_screen: detected same image for 5 seconds, last detected similarity is 50.
3353530196853
[2019-12-23T09:50:15.098 CET] [debug] /var/lib/openqa/share/tests/sle/tests/update/patch_sle.pm:75 called migration::setup_sle
[2019-12-23T09:50:15.098 CET] [debug] <<< testapi::check_screen(mustmatch=[
'tty6-selected',
'text-logged-in-root'
], timeout=60)
[2019-12-23T09:50:15.293 CET] [debug] >>> testapi::_handle_found_needle: found text-login-20180416, similarity 1.00 @ 715/34
[2019-12-23T09:50:15.293 CET] [debug] MMM -> VVVV switch tty_6 successed!

Hi Oliver,

Now in build 108.1, we didn't hit this issue and for further investigation, we'd add some debug info in osinst's
query_isotovideo to see what's happening when we can't switch tty. do you have any ideas on how to fix this ticket?

Thanks!

another try on 44 box: http://10.161.8.44/tests/1031

1. https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/d13647566e5b095b9dc72cb5cc1b0056afdeaaa1#diff-a068d8ac3af290672e4e5a612f1be4e5 overrides the base class post_fail_hook hence there is no check anymore for system responsiveness as is ensured by lib/opensusebasetest . I suggest to call $self->SUPER::post_fail_hook in the post_fail_hook to ensure these checks are done as well.
2. The test module "orphaned_packages_check" is not a good candidate to check for a properly logged in console. I think a better idea would be to call migration/sle12_online_migration/post_migration before console/orphaned_packages_check
3. There should be no need to change os-autoinst as basically the only thing that os-autoinst does is send the hotkey, the check for the right screen after switching is done within https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/susedistribution.pm#L788 so you can simply change test code there to handle the failed detection
4. Please also see all the tickets I linked to the current one

Related case: https://openqa.suse.de/tests/3760131#step/orphaned_packages_check/2

Hi Oliver,
Thanks for the suggest fix, we'll try and see how it works.

Huajian.Luo

with fix it looks good: https://openqa.suse.de/tests/3769437#step/orphaned_packages_check/6
https://openqa.suse.de/tests/3769433#step/orphaned_packages_check/6

with the PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9270 which moves orphaned_package_check to regression test, we don't need to load it during online migration test.

So we'd like to close this ticket by now and for further switch tty issues, we can file with the following ticket. https://progress.opensuse.org/issues/48110

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

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

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_sles15sp1_media_lp-we-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm_all_full
https://openqa.suse.de/tests/3900697

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