action #94069
closedcoordination #71242: [epic] Unify validation in the installed system
Unify test data for guided partitioning
0%
Description
Recently it was created this structure for handling guided partitioning with REST API:
test_data:
guided_partitioning:
filesystem_options:
root_filesystem_type: ext4
Later on we realized it would not be efficient to have a different data structure for each module we create as far as we could use a common shared structure. For expert partitioning we already have that structure:
disks:
- name: vda
table_type: gpt
allowed_unpartitioned: 0.00GB
partitions:
- name: vda2
formatting_options:
filesystem: ext4
mounting_options:
should_mount: 1
mount_point: /
As we can see, we are repeating the information, in this example filesystem 'ext4'.
AC1: Rewrite guided_setup.pm so we can iterate over common structure and extract mount point and filesystem.
AC2: Run verification wherever the module is used (TW x86_64, TW aarch, Leap, SLES, maintenance updates).
Updated by JERiveraMoya over 3 years ago
- Tracker changed from coordination to action
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine to <span style="color:green">qa-yast-to-refine</span>
Updated by JERiveraMoya over 3 years ago
- Tags changed from <span style="color:green">qa-yast-to-refine</span> to qa-yast-to-refine
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine to qa-yast-to-refine, <span style="background-color:lightgreen">Lightgreen Background</span> <span style="background-color:yellow">Yellow Background</span>
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine, <span style="background-color:lightgreen">Lightgreen Background</span> <span style="background-color:yellow">Yellow Background</span> to qa-yast-to-refine, qe-YaST-to-refine
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine, qe-YaST-to-refine to qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement to qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast to qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast, to_refine_qe_yast, to refine qe yast, To Refine QE YaST
Updated by JERiveraMoya over 3 years ago
- Tags changed from qa-yast-to-refine, qe-YaST-to-refine, YaST to refine, qe-yast-refinement, refinement-qe-yast, to_refine_qe_yast, to refine qe yast to qa-yast-to-refine, to refine qe yast
Updated by oorlov over 3 years ago
- Tags changed from qa-yast-to-refine, to refine qe yast to to refine qe yast
Updated by oorlov over 3 years ago
- Tags deleted (
to refine qe yast) - Status changed from New to Workable
Updated by JERiveraMoya over 3 years ago
- Related to action #93641: Create schedules for opensuse test suites added
Updated by oorlov over 3 years ago
Please, create schedule part first (https://progress.opensuse.org/issues/94069), before working on that ticket.
Updated by oorlov over 3 years ago
- Target version changed from SLE 15 SP3 to Current
Updated by JERiveraMoya over 3 years ago
we should wait with this until we progress further with interactive installation, as we might not even need test data if we create separate test modules for each guided setup.
Updated by JERiveraMoya over 2 years ago
- Status changed from New to Rejected
we decided to go for an approach where test data is preferred for validation and during installation we just hardcode what we want, making it more searchable.