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 almost 2 years ago.
Updated over 1 year ago.
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.
- Subject changed from Migrate modify_existing_partition to PowerVM to Migrate modify_existing_partition from PowerKVM to PowerVM
- Related to action #107674: Migrate create_hdd_gnome in Functional group to use AutoYaST added
- Related to deleted (action #107674: Migrate create_hdd_gnome in Functional group to use AutoYaST)
- 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 modify_existing_partition from PowerKVM to PowerVM to Adapt modify_existing_partition to run in PowerVM
- Description updated (diff)
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.
- 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.
- Status changed from Workable to In Progress
- Assignee set to hjluo
START_DIRECTLY_AFTER_TEST=autoyast_mini
- Status changed from In Progress to Resolved
- 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
- Status changed from In Progress to Resolved
Also available in: Atom
PDF