action #116962: Enable PowerVM virtualization in job group 'Migration: Regression' - qe-yam - openSUSE Project Management Tool

Actions

Copy link

action #116962

closed

Enable PowerVM virtualization in job group 'Migration: Regression'

Added by JERiveraMoya over 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

tinawang123

Target version:

Current

Start date:

2022-09-21

Due date:

% Done:

Estimated time:

Description

Motivation¶

In openQA job group 'Migration: Regression' we are still using PowerKVM and from SLE-15-SP2 we stopped supporting it.
We need to move to PowerVM the following existing scenarios:

offline_sles15sp2_ltss_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full
offline_sles15sp3_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full
online_sles15sp2_ltss_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full
online_sles15sp3_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full

Additionally we need to create two additional ones for sles15sp4:

offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full
online_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-py2-tsm-wsm-pcm_all_full

Acceptance criteria¶

AC1: Regression test for ppc64le are running virtualization PowerVM for >=sles15-sp2
AC2: Preparation job (then ones ending in *_pre) are executed using AutoYaST.

Additional info¶

Regression testing is running each job with all product modules, but you can find equivalent jobs in Migration job group that would differ only on that, that they are configured with a specific combination of the product modules. You can borrow the configuration from them.
See current PowerVM jobs for Migration: https://openqa.suse.de/tests/overview?arch=&flavor=&machine=ppc64le-hmc-single-disk&test=&modules=&module_re=&distri=sle&version=15-SP5&build=29.1&groupid=265#

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Subject changed from In job group 'Migration: Regression' we are still using PowerKVM to Enable PowerVM in 'Migration: Regression'
Description updated (diff)

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Description updated (diff)

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Description updated (diff)

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Subject changed from Enable PowerVM in 'Migration: Regression' to Enable PowerVM virtualization in job group 'Migration: Regression'

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

Description updated (diff)

Actions

Copy link

Updated by tinawang123 about 2 years ago

Need update powerVM yaml file.
Add some regression test modules.

Actions

Copy link

Updated by coolgw about 2 years ago

We have not do autoyast install + migration on powerVM before, also for offline case (patch_sle should put in 1st job, otherwise migration task maybe failed), i suppose we need SPIKE task to investigate possibility of basic scenario.

NOTES:following link exist autoyast install+upgrade(x86)
https://openqa.nue.suse.com/tests/9687785#dependencies

Actions

Copy link

Updated by JERiveraMoya about 2 years ago

could you please describe what is the investigation to be needed?
For what I can see there are similar scenarios in "Migration" and "Migration: Regression", so in this ticket for PowerVM we are going to to create an AutoYaST profile to avoid to do a interactive installation in those _pre test suites. It shouldn't change the existing flow, just convert to AutoYaST in PowerVM. For example this test suite is running autoyast in YaST group: https://openqa.suse.de/tests/9679955 so we clone the existing interactive installation and and work with the profile, not much to figure out IMO.

Actions

Copy link

Updated by coolgw about 2 years ago

JERiveraMoya wrote:

could you please describe what is the investigation to be needed?
For what I can see there are similar scenarios in "Migration" and "Migration: Regression", so in this ticket for PowerVM we are going to to create an AutoYaST profile to avoid to do a interactive installation in those _pre test suites. It shouldn't change the existing flow, just convert to AutoYaST in PowerVM. For example this test suite is running autoyast in YaST group: https://openqa.suse.de/tests/9679955 so we clone the existing interactive installation and and work with the profile, not much to figure out IMO.

I have no idea we already have autoyast example in powerVM, that's seems good start point for this ticket.

Actions

Copy link

#10