Project

General

Profile

Actions
Copy link

action #163256

closed

coordination #152769: [epic] Reduction of yaml files in YaST installations

Reduce yaml files for minimal+role_minimal

Added by JERiveraMoya 7 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
zoecao
Target version:
-
Start date:
2024-07-04
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-jul-sprint

Description

Motivation

See epic and tickets in the epic for best practices.

Some general summary as a hint (after reading previous tickets):
Main goals are to reduce for single test suite to single yaml file comparing the ones created per each architecture before and drive the schedule having different yaml default files per each architecture. The final yaml should be stored in a folder where we have the representation of each test case: schedule/yam/test_cases
In order to do that you have to consider if it is just about yaml or would require some code changes to make things more homogeneous, there are multiple approaches ranging from simple dropping small tested functionality in some specific architecture to some more fancy code strategy.
At the same time we should care of variables, basically moving all of them to job group yaml.

Specific from this test suite:
Schedules for this test suite exists in schedule/yast/minimal+role_minimal.

Acceptance criteria

AC1: Reduce yaml files for corresponding test suite over all the architectures
AC2: Clean-up unused files.

Actions
Copy link
 #1

Updated by pstivanin 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to pstivanin
Actions
Copy link
 #2

Updated by pstivanin 6 months ago

  • Status changed from In Progress to Workable
  • Assignee deleted (pstivanin)
Actions
Copy link
 #3

Updated by zoecao 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to zoecao
Actions
Copy link
 #4

Updated by zoecao 6 months ago

Actions
Copy link
 #5

Updated by zoecao 6 months ago

Different with other arches, on s390x, the Systemd default target is set to 'graphical'
https://openqa.suse.de/tests/14992549#
Filed a bug for it: [bsc#1228243]

Actions
Copy link
 #7

Updated by zoecao 6 months ago

The bug ( [bsc#1228243]) was closed as WORKSFORME:

In s390x kvm installation, the Graphical is the expected target. If the installation is done via VNC, then Graphical target is selected independently on the role, see [1]. That machine is supposed to be remotely managed via VNC, so Graphical target would be needed.

[1] https://github.com/yast/yast-services-manager/blob/master/src/lib/services-manager/clients/default_target_proposal.rb#L254.

And in the [PR], skip loading the test module of verify_default_target, and check the default target via test module validate_default_target.

Actions
Copy link
 #8

Updated by zoecao 6 months ago

  • Status changed from In Progress to Resolved

PR and MR were merged, and checked the YaST group yaml, all settings were updated as MR, so resolve here, thanks.

Actions
Copy link

Also available in: Atom PDF