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

not enough capacity in S15-S17. We think it's easy but new test can always have an impact on other stuff. So "easy" but not "trivial".

Triggered once to check feasibility

$ openqa_clone_job_osd --skip-chained-deps 1650904 TEST=yast2_ncurses Y2UITEST_NCURSES=1 EXTRATEST= _GROUP=0

-> https://openqa.suse.de/tests/1656222

hmpf, failed in https://openqa.suse.de/tests/1656222#step/boot_to_desktop/22 with a black screen trying to conduct most likely a remote connection but it is not obvious what is the problem here. blocked by #34003

Do not expect to get unblocked in S19, moving to S20

https://progress.opensuse.org/issues/34003 has been resolved. Unblocking

yes, could be tested against SLE12SP4 or latest SLE15.

$ openqa_clone_job_osd --skip-chained-deps 1749719 TEST=yast2_ncurses Y2UITEST_NCURSES=1 EXTRATEST= _GROUP="Test Development: SLE 15"
Created job #1759484: sle-15-Installer-DVD-s390x-Build665.2-extra_tests_on_gnome@s390x-kvm-sle12 -> https://openqa.suse.de/t1759484

-> https://openqa.suse.de/tests/1759484 failed in https://openqa.suse.de/tests/1759484#step/boot_to_desktop/17

blockers are resolved afaics, so let's put this back to workable

So, as for business value, I've used bugzilla and http://houtsapps01.us.netiq.corp/siebelmatic2/?page=team&searchterm=12 support ticket system to identify used modules.
We are missing a lot of information about product usage, but what I was able to identify is that 'yast dump' YaST module is used on s390x. Majority of issues address installation, so it seems that servers are rarely configured manually or there are no issues with tooling on s390, or everything is configured without YaST modules.