action #124470
[qe-core] Move create_hdd* to use autoyast
100%
Description
To begin with, move the test create_hdd_textmode to use an autoyast profile.
Test sle-15-SP5-Online-x86_64-Build72.1-create_hdd_textmode@64bit : https://openqa.suse.de/tests/10493761#
Subtasks
Related issues
History
#2
Updated by szarate 4 months ago
Updated by - Related to action #120856: [qe-core][leap15.4][update] Remove the create_hdd* tests using interactive installer since we have autoyast added
#4
Updated by szarate 4 months ago
- Related to action #124733: [qe-core] Ensure Libyui is used across where autoyast isn't possible - Wrong product selected during welcome screen. added
Updated by #8
Updated by rfan1 2 months ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16722
We can re-use the autoyast configuration files.
#9
Updated by rfan1 2 months ago
As discussed with Santiago, Yast team has done a lot of work on autoyast_create_hdd_textmode*.
But they may have some other testing purpose to publish the qcow2 images for libyui tests later.
I would suggest if QE-CORE and Yast team can work together for this task.
We can create a basic qcow2 image at first via autoyast and then we can create images for libyui test based on this one.
#10
Updated by rfan1 2 months ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16755
This PR has removed some non-default installed packages in autoyast configuration file.
#12
Updated by rfan1 2 months ago
Create_hdd_gnome_autoyast
are covered by QE-YaST team. Do we need to take them back?
szarate
#13
Updated by szarate about 2 months ago
- Sprint set to QE-Core: April Sprint 23 (Apr 05 - May 03)
- Tags set to qe-core-april-sprint
- Target version set to QE-Core: Ready
#14
Updated by rfan1 about 2 months ago
Private tests are done, let me try to add the tests to job groups (both O3 and OSD)
OSD name - > create_hdd_textmode_autoyast
O3 name - > create_hdd_textmode_autoyast
#15
Updated by rfan1 about 2 months ago
- % Done changed from 0 to 60
I will try to cover create_hdd_textmode autoyast on xen_pv and xen_hvm platforms as well
Seems there are more steps needed for xen platform. let me skip this for now
https://10.160.0.207/tests/overview?build=rfan0412&distri=sle&version=15-SP5
#16
Updated by dzedro about 2 months ago
Updated by There should be at least one non-autoyast installation, there were yast bugs which didn't show up in auotyast installation.
I can't say what test should be left as non-autoyast installation, I guess it can be qam-gnome, there are not big differences between installation except patterns.
#17
Updated by rfan1 about 2 months ago
dzedro wrote:
There should be at least one non-autoyast installation, there were yast bugs which didn't show up in auotyast installation.
I can't say what test should be left as non-autoyast installation, I guess it can be qam-gnome, there are not big differences between installation except patterns.
Thanks much! it makes sense.
For products in development phase [sle15sp5/TW], I will keep both interactive installation and autoyast ones to make sure we don't lose coverage.
For QEM, I agree with you. I will keep some jobs which don't have dependency.
#18
Updated by rfan1 about 2 months ago
- Status changed from In Progress to Feedback
#19
Updated by rfan1 about 1 month ago
- Copied to action #128339: [qe-core][functional] children jobs use the qcow2 image which created via autoyast added