action #110779
closed
coordination #110770: [Epic] Remove dependency of create_hdd_gnome in PowerKVM in YaST group
Test yast modules in PowerVM enabling libyui REST in AutoYaST profile
Added by JERiveraMoya almost 2 years ago.
Updated over 1 year ago.
Description
Motivation¶
See parent task #110770
We have this dependency chain:
create_hdd_gnome ---> create_hdd_gnome_libyui ---> yast2_ncurses_gnome
|-->yast2_gui
As we don't need to cover in PowerVM GUI applications, we just need to migrate 'yast2_ncurses_gnome', but at the same time we don't need a gnome image to be used with ncurses, we just need a textmode one including the development module.
Therefore in this ticket we will be creating an AutoYaST test suite which will take care of installing libyui-rest-api and adding the port for the firewalld, replacing completely this test suite https://openqa.suse.de/tests/9564402#step/firewalld_add_port/1
Acceptance criteria¶
AC1: Create new AutoYaST test suite in textmode for PowerVM which install necessary product modules and configure libyui REST to be used
AC2: Setup yast2_ncurses for this architecture to start directly after this new ay profile
AC3: Do not run yast2_gui for ppc64le
Additional information¶
Use openQA setting to create the connection: 'START_DIRECTLY_AFTER_TEST'
- Description updated (diff)
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Workable
- Tags set to qe-yast-refinement
- Description updated (diff)
- Status changed from Workable to New
- Subject changed from Migrate test suite 'create_hdd_gnome_libyui' from PowerKVM to PowerVM to Test yast modules in for PowerVM enabling libyui REST in AutoYaST profile
- Description updated (diff)
- Subject changed from Test yast modules in for PowerVM enabling libyui REST in AutoYaST profile to Test yast modules in PowerVM enabling libyui REST in AutoYaST profile
My understanding we ONLY need two job complete task, or even one simple job finish task if we only check yast2_ncurses
First job(autoyast install) + second job(libyu setup + yast2_ncurses_gnome)
From my understanding we just need the autoyast part to setup a text image and then we should run yast2_ncurses.
Still open questions:
we have
- yast2_ncurses_textmode.yaml
- yast2_ncurses_texxtpmode_pvm.yaml
in the yaml schedules, but both seem to be needle based instead of libyui based. So question remaining is
if we need to create a yast2_ncurses that uses libyui instead of the needle based tests.
coolgw wrote:
My understanding we ONLY need two job complete task, or even one simple job finish task if we only check yast2_ncurses
First job(autoyast install) + second job(libyu setup + yast2_ncurses_gnome)
the libyui setup part will be included in the autoyast profile.
only ncurses is tested afterwards, not gnome.
rainerkoenig wrote:
From my understanding we just need the autoyast part to setup a text image and then we should run yast2_ncurses.
It is more than a textmode image, it will include development (possibly desktop module as well because it is a dependency) module and firewall adjustments.
Still open questions:
we have
- yast2_ncurses_textmode.yaml
- yast2_ncurses_texxtpmode_pvm.yaml
in the yaml schedules, but both seem to be needle based instead of libyui based. So question remaining is
if we need to create a yast2_ncurses that uses libyui instead of the needle based tests.
good catch, but yeah, the intention is to also test in the future libyui for ncurses, so we should have the right setup without using gnome (that is something done for historic reasons).
JERiveraMoya wrote:
rainerkoenig wrote:
From my understanding we just need the autoyast part to setup a text image and then we should run yast2_ncurses.
It is more than a textmode image, it will include development (possibly desktop module as well because it is a dependency) module and firewall adjustments.
Still open questions:
we have
- yast2_ncurses_textmode.yaml
- yast2_ncurses_texxtpmode_pvm.yaml
in the yaml schedules, but both seem to be needle based instead of libyui based. So question remaining is
if we need to create a yast2_ncurses that uses libyui instead of the needle based tests.
good catch, but yeah, the intention is to also test in the future libyui for ncurses, so we should have the right setup without using gnome (that is something done for historic reasons).
So for scope question, test yast2_ncurses with libyui or without?
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Workable
coolgw wrote:
JERiveraMoya wrote:
rainerkoenig wrote:
From my understanding we just need the autoyast part to setup a text image and then we should run yast2_ncurses.
It is more than a textmode image, it will include development (possibly desktop module as well because it is a dependency) module and firewall adjustments.
Still open questions:
we have
- yast2_ncurses_textmode.yaml
- yast2_ncurses_texxtpmode_pvm.yaml
in the yaml schedules, but both seem to be needle based instead of libyui based. So question remaining is
if we need to create a yast2_ncurses that uses libyui instead of the needle based tests.
good catch, but yeah, the intention is to also test in the future libyui for ncurses, so we should have the right setup without using gnome (that is something done for historic reasons).
So for scope question, test yast2_ncurses with libyui or without?
doesn't matter if we don't have modules that use libyui for now, we should schedule the setup module, so it will be ready to include in the future any module that we consider (just one line), so yes, with libyui-rest-api.
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF