Project

General

Profile

Actions

coordination #110770

closed

[Epic] Remove dependency of create_hdd_gnome in PowerKVM in YaST group

Added by JERiveraMoya almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-05-09
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

There is not support for PowerKVM since a time ago:
https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS916-171/index.html
and we have this bug which is not going to be resolved any time soon. In particular this issue is an impediment to be able to boot after AutoYaST installation in ppc64le PowerKVM (it is not sporadic regarless what the bug says).

The reason why in openQA we still use PowerKVM is due to PowerVM doesn't support snapshots at the moment , so we need to run more times the previous steps in chained jobs as they cannot be simply reused using a qcow2 for example, like we do in other architectures.

Nevertheless when PowerKVM doesn't fit our expectations or test start to be flaky there is not reason to keep them, for example our test case for cloning and reinstall the system is already covered with PowerVM, so we don't need to keep failing this scenario anymore:
https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/405

During the effort to try to covert all the create_hdd_gnome jobs to AutoYaST we found this impediment. There a plenty of jobs chained so it is not as simple as remove it. Also it is not worth the effort to migrate it to libyui REST for now and introduce in Functional job group, it is a possibility but doesn't make much sense to enhance something obsolete. What we could do instead is to incorporate required steps from parent job, the create_hdd_gnome for PowerVM to the chained jobs belonging to YaST job group.

In that sense we would make YaST job group more robust, and in the future other job groups can potentially do the same, because with less dependencies for the remaining part, not being able to save snapshots and repeating the steps in a few places will be acceptable.

Acceptance criteria

AC1: For after-installation test suite to be migrated, run new auto-installation using PowerVM equivalent to 'create_hdd_gnome'
AC2: For after-installation test suite to be migrated, directly chain that auto-installation with new PowerVM testsuites equivalent to existing chained test suites in PowerKVM
AC3: For installation test suites to be migrated, adjust with existing libyui test modules and make some disk adjustments as pre-requirement.

Further info

See ticket in this epic to distingish between after-installation case and installation case.
Dependencies: https://openqa.suse.de/tests/9564005#dependencies


Subtasks 3 (0 open3 closed)

action #110773: Adapt modify_existing_partition to run in PowerVMResolvedhjluo2022-05-09

Actions
action #110776: Migrate sles+sdk+proxy_SCC_via_YaST from PowerKVM to PowerVMResolvedzoecao2022-05-09

Actions
action #110779: Test yast modules in PowerVM enabling libyui REST in AutoYaST profileResolvedcoolgw2022-05-09

Actions

Related issues 2 (0 open2 closed)

Related to qe-yam - action #107674: Migrate create_hdd_gnome in Functional group to use AutoYaSTClosedgeor2022-02-28

Actions
Related to qe-yam - coordination #116680: [Epic] Move test suites to PowerVM in YaST groupResolved2022-10-04

Actions
Actions #1

Updated by JERiveraMoya almost 2 years ago

  • Subject changed from Remove dependency of create_hdd_gnome in of PowerKVM in YaST group to [Epic] Remove dependency of create_hdd_gnome in of PowerKVM in YaST group
Actions #2

Updated by JERiveraMoya almost 2 years ago

  • Related to action #107674: Migrate create_hdd_gnome in Functional group to use AutoYaST added
Actions #3

Updated by JERiveraMoya almost 2 years ago

  • Subject changed from [Epic] Remove dependency of create_hdd_gnome in of PowerKVM in YaST group to [Epic] Remove dependency of create_hdd_gnome in PowerKVM in YaST group
Actions #4

Updated by JERiveraMoya almost 2 years ago

  • Description updated (diff)
Actions #5

Updated by JERiveraMoya almost 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #6

Updated by JERiveraMoya over 1 year ago

  • Description updated (diff)
Actions #7

Updated by JERiveraMoya over 1 year ago

  • Tags set to qe-yast-refinement
  • Description updated (diff)
  • Status changed from Workable to New
Actions #8

Updated by JERiveraMoya over 1 year ago

Actions #9

Updated by JERiveraMoya over 1 year ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable
Actions #10

Updated by JERiveraMoya over 1 year ago

  • Status changed from Workable to Resolved
  • Assignee set to JERiveraMoya
Actions

Also available in: Atom PDF