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.

Same problem:
https://openqa.suse.de/tests/3767738#step/yast2_migration/23

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

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

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 :)

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