Project

General

Profile

Actions

action #124470

closed

[qe-core] Move create_hdd* to use autoyast

Added by dvenkatachala over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
2023-04-11
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:
Sprint:
QE-Core: May Sprint 23 (May 10 - May 31)

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 1 (0 open1 closed)

action #127472: [qe-core][qem] move create_hdd* to use AutoyastResolvedrfan12023-04-11

Actions

Related issues 4 (1 open3 closed)

Related to openQA Tests - action #120856: [qe-core][leap15.4][update] Remove the create_hdd* tests using interactive installer since we have autoyastClosedrfan12022-08-30

Actions
Related to openQA Tests - action #124733: [qe-core] Ensure Libyui is used across where autoyast isn't possible - Wrong product selected during welcome screen.Workable2023-02-17

Actions
Copied to openQA Tests - action #128339: [qe-core][functional] children jobs use the qcow2 image which created via autoyastResolvedrfan12023-04-11

Actions
Copied to openQA Tests - action #134429: [qe-core][functional][sle15sp6] Move create_hdd* to use autoyastResolvedrfan1

Actions
Actions #2

Updated by szarate over 1 year ago

  • Related to action #120856: [qe-core][leap15.4][update] Remove the create_hdd* tests using interactive installer since we have autoyast added
Actions #3

Updated by szarate over 1 year ago

  • Subject changed from [qe-core] Implement autoyast installation for create_hdd* test to [qe-core] Move create_hdd* to use autoyast
  • Description updated (diff)
Actions #4

Updated by szarate over 1 year ago

  • Related to action #124733: [qe-core] Ensure Libyui is used across where autoyast isn't possible - Wrong product selected during welcome screen. added
Actions #5

Updated by rfan1 about 1 year ago

  • Assignee set to rfan1
Actions #6

Updated by rfan1 about 1 year ago

Will handle SLE15SP5/TW with textmode at first.

Actions #7

Updated by rfan1 about 1 year ago

  • Status changed from New to In Progress
  • Start date changed from 2023-02-14 to 2023-03-30
Actions #8

Updated by rfan1 about 1 year ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16722

We can re-use the autoyast configuration files.

Actions #9

Updated by rfan1 about 1 year 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.

Actions #10

Updated by rfan1 about 1 year 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.

Actions #11

Updated by rfan1 about 1 year ago

Now create_hdd_textmode_autoyast tests are passed on both SLE15SP5 and TW:
TW
SLE

SPVM test is failed due to infra issue

Actions #12

Updated by rfan1 about 1 year ago

Create_hdd_gnome_autoyast
are covered by QE-YaST team. Do we need to take them back?
@szarate

Actions #13

Updated by szarate about 1 year 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
Actions #14

Updated by rfan1 about 1 year 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

Actions #15

Updated by rfan1 about 1 year 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

Actions #16

Updated by dzedro about 1 year ago

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.

Actions #17

Updated by rfan1 about 1 year 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.

Actions #18

Updated by rfan1 about 1 year ago

  • Status changed from In Progress to Feedback
Actions #19

Updated by rfan1 about 1 year ago

  • Copied to action #128339: [qe-core][functional] children jobs use the qcow2 image which created via autoyast added
Actions #20

Updated by szarate about 1 year ago

  • Sprint changed from QE-Core: April Sprint 23 (Apr 05 - May 03) to QE-Core: May Sprint 23 (May 10 - May 31)
Actions #21

Updated by rfan1 about 1 year ago

  • Status changed from Feedback to Resolved
Actions #22

Updated by rfan1 9 months ago

  • Copied to action #134429: [qe-core][functional][sle15sp6] Move create_hdd* to use autoyast added
Actions

Also available in: Atom PDF