Project

General

Profile

Actions

action #126125

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

As disk space limit, we need reduce modules for regression migration cases at powerVM

Added by tinawang123 about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2023-03-17
Due date:
% Done:

0%

Estimated time:

Description

Motivation

As powerVM only have 18G disk space.
It's not enough space to test all modules at spvm as we normally do in Migration: Misc. in regression flavor.
It will report error message: https://openqa.suse.de/tests/10706024#step/await_install/57
We need reduce modules for those cases.
We still want to keep those pre and post check service and install all patterns, so basically the only modification is the number of products modules/extensions used in the scenarios.

Example of failures, but mostly all affected (even if the error is different):
https://openqa.suse.de/tests/10706024#step/await_install/53
https://openqa.suse.de/tests/10706602#step/await_install/9
https://openqa.suse.de/tests/10705943#step/await_install/30

Acceptance criteria

AC1: Reduce the number of product modules/extensions in powerVM scenarios for Regression so the scenarios pass

Additional information

Consider to keep product modules in this order for example: basesystem, server, desktop, development, python3, legacy, web and scripting, transactional, containers, public cloud (but it is just a suggestion, from what looks more basic and what it looks more additional, but of course depends how the customer uses, but in this case we are just putting some effort in having all together, for PowerVM we actually don't know, in YaST we only select textmode for example, so take it as orientation).

Product modules and extension for these jobs needs to be deselected in the parent jobs.

Actions #1

Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Current
  • Parent task set to #121876
Actions #2

Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)
Actions #3

Updated by hjluo about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #4

Updated by hjluo about 1 year ago

Current:

  • for 15.5 migration it set SCC_ADDONS=base,serverapp,desktop,
  • for parent SCC_ADDONS=base,serverapp,desktop,dev,contm,lgm,python2,tsm,wsm,live,pcm,ltss
Actions #5

Updated by hjluo about 1 year ago

Actions #6

Updated by hjluo about 1 year ago

try with 15SP2:

Actions #7

Updated by JERiveraMoya about 1 year ago

  • Priority changed from Normal to High
Actions #9

Updated by hjluo about 1 year ago

15SP4 which just deletes the snapshot to see
the avail from
https://openqa.suse.de/tests/10844578#step/patch_sle/178 1.9G to
https://openqa.suse.de/tests/10844578#step/shutdown/5 4.3G

Actions #10

Updated by hjluo about 1 year ago

  • MR: 282
  • PR: 16816 Merged
  • Now the VRs were blocked by worker unstable
Actions #11

Updated by hjluo about 1 year ago

Now this ticket was blocked by the availability of the spvm worker to run the test, most spvm workers were not working and failed at beginning. and we're thinking of moving worker from spvm to hmc.

Actions #12

Updated by hjluo about 1 year ago

now try to reduce modules in the dev group SPVM,once the workers are working now.

Actions #13

Updated by JERiveraMoya about 1 year ago

  • Priority changed from High to Normal
Actions #14

Updated by hjluo about 1 year ago

In milestone, we still hit this for case:

  • case Name: Milestone-ppc64le-Build93.2-offline_sles15sp2_ltss_media_basesys-srv-desk-dev_all_full@ppc64le-spvm
  • Failed case: disk_full
Actions #15

Updated by JERiveraMoya about 1 year ago

Merged, could you please rerun scenarios failing with new configuration to be sure it worked?

Actions #16

Updated by hjluo about 1 year ago

OK. will add another MR for the milestone.
MR: 291

Actions #17

Updated by JERiveraMoya about 1 year ago

hjluo wrote:

OK. will add another MR for the milestone.
MR: 291

This MR is not only for Milestone, you keep removing product modules.
I noticed one test suite:
offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-tsm-wsm-py3-pcm_all_full now only installs base and server.
Could you double check that the names of the test suite reflect what they install.
Additionally check if the test matrix for migration requires some update.

Actions #18

Updated by hjluo about 1 year ago

JERiveraMoya wrote:

hjluo wrote:

OK. will add another MR for the milestone.
MR: 291

This MR is not only for Milestone, you keep removing product modules.
I noticed one test suite:
offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-tsm-wsm-py3-pcm_all_full now only installs base and server.
Could you double-check that the names of the test suite reflect what they install?
Additionally check if the test matrix for migration requires some update.

Actions #19

Updated by leli about 1 year ago

hjluo wrote:

JERiveraMoya wrote:

hjluo wrote:

OK. will add another MR for the milestone.
MR: 291

This MR is not only for Milestone, you keep removing product modules.
I noticed one test suite:
offline_sles15sp4_pscc_lp-basesys-srv-desk-dev-contm-lgm-tsm-wsm-py3-pcm_all_full now only installs base and server.
Could you double-check that the names of the test suite reflect what they install?
Additionally check if the test matrix for migration requires some update.

Hi Huajian, please take care to remove modules from the list, at least the dev(sdk) depend on desktop application, so you can't remove desk while reserve dev(sdk).

Actions #20

Updated by JERiveraMoya about 1 year ago

  • Status changed from In Progress to Resolved

thanks, re-open if you see more failure in GMC.

Actions

Also available in: Atom PDF