action #119950
Updated by JERiveraMoya over 1 year ago
#### Observation
openQA test in scenario sle-15-SP5-Migration-from-SLE15-SPx-ppc64le-ha_migration_online_pscc_sles15sp4@ppc64le-hmc-single-disk fails in
[yast2_migration](https://openqa.suse.de/tests/9873489/modules/yast2_migration/steps/25)
Apparently automation fails to complete registration phase, very likely because we force to user ssh forwarding when running qt in remote worker, like in this case for PowerVM. Using ncurses should accelerate the process.
Of course the problem behind the scene are networking issues with PowerVM, but let's tackle this first.
#### Scope
All test suite using PowerVM in all Migration job groups.
#### Acceptance criteria
**AC1**: Research the reason why we shouldn't test qt, is it because our testing infrastructure?
**AC2**: Run always yast2_migration in PowerVM with ncurses instead of qt
#### Additional information
- For instance we open sw_single in this way in `yast2_i`: `my $module_name = y2_module_consoletest::yast2_console_exec(yast2_module => 'sw_single', yast2_opts => '--ncurses');`
- A better solution which would not require to add always this `yast2_opts` parameter is to ensure that the target desktop in the AutoYaST image used by this job is textmode, even if the default is gnome for PowerVM is a special case and we might need to edit this AutoYaST profile to force that.