action #119950

Run yast2_migration in PowerVM only with ncurses

Added by coolgw 3 months ago. Updated about 2 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario sle-15-SP5-Migration-from-SLE15-SPx-ppc64le-ha_migration_online_pscc_sles15sp4@ppc64le-hmc-single-disk fails in

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.


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.


#1 Updated by maritawerner 3 months ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)

#2 Updated by JERiveraMoya 3 months ago

  • Tags set to qe-yast-refinement
  • Subject changed from test fails in yast2_migration - no license page / update repo page show to Run yast2_migration in PowerVM only with ncurses
  • Description updated (diff)
  • Target version set to Current

#3 Updated by JERiveraMoya 3 months ago

  • Description updated (diff)

#4 Updated by JERiveraMoya 3 months ago

  • Priority changed from Normal to High

#5 Updated by JERiveraMoya 3 months ago

  • Tags deleted (qe-yast-refinement)
  • Description updated (diff)
  • Status changed from New to Workable

#6 Updated by jgwang 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jgwang

#7 Updated by jgwang 2 months ago

I committed PR to always run yast2_migration in PowerVM with ncurses

please help to review it.

#8 Updated by jgwang 2 months ago

running the current tests in textmode is enough to PowerVM, and it will
not be stable to make tests run ssh forwarding the graphical part, I don't
notice the requirement that tests must be run with graphical on PowerVM,
so we can deal with tests with graphical if there is a requirement later.

#9 Updated by jgwang 2 months ago

I checked the system on PowerVM after installation with graphical target,
and found that no graphics device on PowerVM and Xorg failed to launch like

[    97.196] (II) LoadModule: "fbdevhw"
[    97.196] (II) Loading /usr/lib64/xorg/modules/
[    97.196] (II) Module fbdevhw: vendor="X.Org Foundation"
[    97.196]    compiled for 1.20.3, module version = 0.0.2
[    97.196]    ABI class: X.Org Video Driver, version 24.0
[    97.196] (EE) open /dev/fb0: No such file or directory
[    97.196] (EE) No devices detected.
[    97.196] (EE)
Fatal server error:
[    97.196] (EE) no screens found(EE)
[    97.196] (EE)
Please consult the The X.Org Foundation support
 for help.
[    97.197] (EE) Please also check the log file at "/var/log/Xorg.5.log" for additional information.
[    97.197] (EE)
[    97.197] (EE) Server terminated with error (1). Closing log file.

I think that the current configuration of PowerVM is not able to start the
normal GUI, and the Qt scenario is not normal although Qt interface is OK
by ssh X11 forwarding.
anyway, I think textmode is enough to PowerVM.

#10 Updated by coolgw about 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF