Project

General

Profile

Actions

action #179026

open

coordination #169654: [epic] Create test scenarios for Agama

Create unattended scenario with home encrypted and resizing

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

Status:
In Progress
Priority:
High
Assignee:
Target version:
-
Start date:
2025-03-17
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We should cover also capabilities of profiles for resizing partition https://agama-project.github.io/docs/user/unattended/storage#deleting-and-shrinking-existing-devices and because changing size of default product partition to allocate a home is a perfect simple example of that we could even add a home encrypted, which is also a typical case in openSUSE.

The idea could be to try to run in all architectures after our existing sles_default_unattended (where we will publish qcow2 or we will use START_DIRECTLY_AFTER_TEST) and that system will have / and swap with default sizes.
Then we will run unattended installation resizing both partition and allocating space for a new encrypted /home.

{
  "storage": {
    "drives": [
      {
        "search": "/dev/vda",
        "partitions": [
          { 
            "search": "/dev/vda2",
            "filesystem": { "path": "/" },
            "size": {
              "min": "2 GiB",
              "max": "current"
            }
          },
          {
            "search": "/dev/vda3",
            "filesystem": { "path": "swap" },
            "size": "1 GiB"
          },
          { 
            "filesystem": { "path": "/home" },
            "encryption": {
              "luks2": { "password": "12345" }
            }
          }
        ]
      }
    ]
  }
}

Acceptance criteria

  • AC1: Create profile and test suite that can run in all architectures which create encrypted home and resize existing partitioning.
Actions #1

Updated by hjluo about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #2

Updated by JERiveraMoya about 1 month ago

  • Status changed from In Progress to Workable
Actions #3

Updated by JERiveraMoya about 1 month ago

  • Assignee deleted (hjluo)
Actions #4

Updated by leli 25 days ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions #5

Updated by JERiveraMoya 24 days ago

  • Tags changed from qe-yam-mar-sprint-fy25 to qe-yam-apr-sprint-fy25
Actions #6

Updated by leli 19 days ago

Now VR ready on qemu backend, https://openqa.suse.de/tests/overview?distri=sle&version=16.0&build=73.1&groupid=316 Still working on s390x and ppc64le.

Actions #7

Updated by JERiveraMoya 18 days ago

leli wrote in #note-6:

Now VR ready on qemu backend, https://openqa.suse.de/tests/overview?distri=sle&version=16.0&build=73.1&groupid=316 Still working on s390x and ppc64le.

Please, avoid presenting the result of the verification without open PR, to know what kind of hacks you are doing would help to understand if really worth for example have s390x/ppc64le (but it is kind of good idea if we could have it in the remote architectures, now that more than one person in the team mentioned).

Actions

Also available in: Atom PDF