Project

General

Profile

action #61877

[SLE][Migration][SLE15SP2] test fails in yast2_migration - no candidate needle with tag(s) 'yast2-migration-installupdate, yast2-migration-proposal' matched

Added by tinawang123 about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-01-08
Due date:
% Done:

100%

Estimated time:
12.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Migration-from-SLE15-SPX-to-SLE15-SP2-x86_64-online_sled15sp1_pscc_basesys_desk_we_dev_py2_all_full_y@64bit_cirrus fails in
yast2_migration

Test suite description

Reproducible

Fails since (at least) Build 93.1

Further details

Always latest result in this scenario: latest


I think it not only needles problem. Need check more

History

#1 Updated by leli about 3 years ago

  • Assignee set to leli
  • Estimated time set to 12.00 h

#2 Updated by leli about 3 years ago

The needle is not matched in time since VNC is stalled. See log info:

[2020-01-07T17:59:43.339 CET] [debug] considering VNC stalled, no update for 4.01 seconds

We can keep an eye on this issue for several builds.

#4 Updated by leli about 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

#5 Updated by okurz almost 3 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: online_sled15sp1_pscc_basesys_desk_we_dev_py2_all_full_y
https://openqa.suse.de/tests/3857588

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

#6 Updated by okurz almost 3 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: online_sled15sp1_pscc_basesys_desk_we_dev_py2_all_full_y
https://openqa.suse.de/tests/3892154

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

#7 Updated by leli almost 3 years ago

  • Priority changed from Normal to High

#8 Updated by leli almost 3 years ago

  • Priority changed from High to Urgent

#9 Updated by leli almost 3 years ago

This issue is for the old needle of yast2-migration-target doesn't cover the next button which cause the system is not ready to accept 'next' key even the needle matched. With Oliver's help, I have removed invalid needles "yast2_migration-yast2-migration-installupdate-20190923" and yast2-migration-target then create correct needle.
After this action, I can't find the issue in recent 3 builds. Thanks @Oliver.

See:

As you asked me for advice I looked into the issue in more detail and I found one of the common problems: Most likely there is no real issue with sending key presses but that the prerequisites are not properly fulfilled and it already starts in L204 . See https://openqa.suse.de/tests/3760125#step/yast2_migration/18 . The needle does not assert that the "Next" key is shown properly, hence the system might not yet be fully ready. Then afterwards similar problematic needles are used. The needle "yast2_migration-yast2-migration-installupdate-20190923" in http://openqa.nue.suse.com/tests/3946437#step/yast2_migration/37 is wrong. It does not assert the system to be in a ready state to process any next step. It must be deleted and replaced by a proper one. For reference take a look in https://openqa.opensuse.org/tests/1193215#step/installation_overview/1 . The "inst-overview" needle not only looks for text within the text box but also that the "install" button is ready. Also in https://openqa.suse.de/tests/3760125#step/yast2_migration/21 the migration target is checked but not that the page is fully loaded as the description text is not yet shown. This can also explain why a system does not react to key presses yet.

EDIT: I know added a section https://progress.opensuse.org/projects/openqatests/wiki/Wiki#ensure-prerequisites-for-next-test-steps , thanks for the incentive :)

=====================================

#10 Updated by leli almost 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

I have run the failed case 100 times, 99 passed and 1 failed for SCC network issue.
https://openqa.nue.suse.com/tests?match=lemon_poo#61877

Also available in: Atom PDF