Project

General

Profile

Actions
Copy link

action #110773

closed

coordination #110770: [Epic] Remove dependency of create_hdd_gnome in PowerKVM in YaST group

Adapt modify_existing_partition to run in PowerVM

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

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

0%

Estimated time:

Description

Motivation

See parent task #110770

Scope

modify_existing_partition run only in YaST group in ppc64le
https://openqa.suse.de/tests/9758750

Acceptance criteria

AC1: Create autoinstallation with AutoYaST which does similar setup (some default installation) than create_hdd_gnome
AC2: Adapt modify_existing_partition to run in PowerVM

Suggestions

In PowerVM we do some actions to wipe out the disks so we can have fixed expectation:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/bootloader_pvm.pm#L135
We could do something similar here after wiping out in order to prepare the disk in similar fashion than for qemu is done in the parent job that is booted. That would save us to run AutoYaST directly chained here.
I don't think we can run by command this setup, it is easier to have and auto-installation directly chained.
In Functional groups we created: autoyast_create_hdd_gnome which should be a starting point. For all those AutoYaST create_hdd_gnome in Functional we will need a copy in our job group in the near future, so the AutoYaST image for this job would complete that work for the arch missing.

Actions
Copy link
 #1

Updated by JERiveraMoya over 2 years ago

  • Subject changed from Migrate modify_existing_partition to PowerVM to Migrate modify_existing_partition from PowerKVM to PowerVM
Actions
Copy link
 #2

Updated by JERiveraMoya over 2 years ago

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

Updated by JERiveraMoya over 2 years ago

  • Related to deleted (action #107674: Migrate create_hdd_gnome in Functional group to use AutoYaST)
Actions
Copy link
 #4

Updated by JERiveraMoya over 2 years ago

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

Updated by JERiveraMoya about 2 years ago

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

Updated by JERiveraMoya about 2 years ago

  • Subject changed from Migrate modify_existing_partition from PowerKVM to PowerVM to Adapt modify_existing_partition to run in PowerVM
  • Description updated (diff)
Actions
Copy link
 #7

Updated by coolgw about 2 years ago

I suppose we need wipe out disk ONLY we find issue blocked Adapt work? Normally if you use same worker the default disk setup(size etc..) is same. Correct me if i am wrong.

Actions
Copy link
 #8

Updated by JERiveraMoya about 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Description updated (diff)
  • Status changed from New to Workable

coolgw wrote:

I suppose we need wipe out disk ONLY we find issue blocked Adapt work? Normally if you use same worker the default disk setup(size etc..) is same. Correct me if i am wrong.

yes, you are right, let's run AutoYaST first and START_DIRECTLY_AFTER_TEST for this test suite.

Actions
Copy link
 #9

Updated by hjluo about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions
Copy link
 #10

Updated by hjluo about 2 years ago

START_DIRECTLY_AFTER_TEST=autoyast_mini

Actions
Copy link
 #11

Updated by JERiveraMoya about 2 years ago

autoyast mini has another purpose which is test minimal AutoYaST profile, let's have a duplication for now and think later how to optimize.
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=autoyast_create_hdd_gnome&modules=&module_re=&distri=sle&version=15-SP5&build=32.1&groupid=110#
here there are the test suite that are doing AutoYaST and we are missing PowerVM, but we have plan to move all these test suite to YaST group, so you can set this new test suite that is using mini profile (for now) to set up in YaST group, instead of in functional. We can follow the same naming that those other test suite but this new test suite.

Actions
Copy link
 #13

Updated by hjluo about 2 years ago

  • Status changed from In Progress to Resolved

PR merged.

Actions
Copy link
 #14

Updated by JERiveraMoya almost 2 years ago

  • Status changed from Resolved to In Progress

Please, read my comment about AutoYaST mini, we don't want this dependency: https://openqa.suse.de/tests/9969365#dependencies, because when something will go wrong, we will be updating that mini profile and that has a different purpose for testing. Just duplicate it and call it with a different name as suggested autoyast_create_hdd_gnome

Actions
Copy link
 #15

Updated by JERiveraMoya almost 2 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #16

Updated by JERiveraMoya almost 2 years ago

thanks for the change!

Actions
Copy link

Also available in: Atom PDF