action #107674
closed
coordination #107668: [Epic] Support creation of images in other groups using AutoYaST
Migrate create_hdd_gnome in Functional group to use AutoYaST
Added by JERiveraMoya over 2 years ago.
Updated over 2 years ago.
Description
Motivation¶
Ensure that AutoYaST works fine in all architecture and give a head start to QE-Core squad to implement the rest of the create_hdd scenarios in the near future.
Acceptance criteria¶
AC1: Migrate create_hdd_gnome in Functional group to use AutoYaST.
AC2: Ensure dependent job run without problems (image created is similar/equal to the one created with AutoYaST)
Further information¶
Check this example of migration for x86_64: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14354
Basic steps are as follows:
- Recover cloned AutoYaST profile via yast2 clone_system.
- Prepare test suite that use that profile and keep same setting than original job for publishing images, ensuring also that the dependencies works fine.
- For svirt-xen we might not have any example in YaST group but in theory should work.
- Description updated (diff)
- Subject changed from Create AutoYaST profiles for create_hdd_gnome scenarios to Migrate create_hdd_gnome in Functional group to use AutoYaST
- Description updated (diff)
- Tags deleted (
qe-yast-refinement)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to geor
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimal+base
https://openqa.suse.de/tests/8407804#step/select_patterns/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 32 days if nothing changes in this ticket.
wrong labeling related to that reminder, fixed.
Hello @szarate,
As offline discussion with Joaquin, as his kindly suggestion:
if you find some time in your team for creating some of those AutoYaST profiles (even if it is only for one architecture), let use know in the ticket related to the PR, so Santi or me are aware to not repeat the work. We can assist for sure.
security team has a test scenario which use AUTOyast profile to install the OS:
https://openqa.suse.de/tests/8569578
It is about LUKS2 encryption for root disk [btw we didn't publish any qcow2 image there]
- Status changed from In Progress to Closed
Great job @george, I will create tickets in this epic for remaining parts:
- Related to action #110773: Adapt modify_existing_partition to run in PowerVM added
- Related to deleted (action #110773: Adapt modify_existing_partition to run in PowerVM)
- Related to coordination #110770: [Epic] Remove dependency of create_hdd_gnome in PowerKVM in YaST group added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: allpatterns
https://openqa.suse.de/tests/8755941#step/disable_grub_timeout/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Status changed from Closed to Feedback
- Status changed from Feedback to Closed
Also available in: Atom
PDF