Project

General

Profile

action #94069

coordination #71242: [epic] Unify validation in the installed system

Unify test data for guided partitioning

Added by JERiveraMoya about 1 month ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2021-06-16
Due date:
% Done:

0%

Estimated time:

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).


Related issues

Related to qe-yast - action #93641: Create schedules for opensuse test suitesClosed2021-06-08

History

#1 Updated by JERiveraMoya about 1 month ago

  • Tracker changed from coordination to action

#2 Updated by JERiveraMoya about 1 month ago

  • Tags changed from qa-yast-to-refine to <span style="color:green">qa-yast-to-refine</span>

#3 Updated by JERiveraMoya about 1 month ago

  • Tags changed from <span style="color:green">qa-yast-to-refine</span> to qa-yast-to-refine

#4 Updated by JERiveraMoya about 1 month 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>

#5 Updated by JERiveraMoya about 1 month 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

#6 Updated by JERiveraMoya about 1 month 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

#7 Updated by JERiveraMoya about 1 month 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

#8 Updated by JERiveraMoya about 1 month 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

#9 Updated by JERiveraMoya about 1 month 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

#10 Updated by oorlov about 1 month ago

  • Tags changed from qa-yast-to-refine, to refine qe yast to to refine qe yast

#11 Updated by oorlov about 1 month ago

  • Tags deleted (to refine qe yast)
  • Status changed from New to Workable

#12 Updated by JERiveraMoya about 1 month ago

  • Related to action #93641: Create schedules for opensuse test suites added

#13 Updated by oorlov about 1 month ago

Please, create schedule part first (https://progress.opensuse.org/issues/94069), before working on that ticket.

#14 Updated by oorlov 10 days ago

  • Target version changed from SLE 15 SP3 to Current

#15 Updated by JERiveraMoya 2 days ago

  • Status changed from Workable to New

#16 Updated by JERiveraMoya 2 days 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.

Also available in: Atom PDF