Project

General

Profile

Actions

action #178723

closed

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

Create new test scenario to format directly home and configure boot partition in a different disk

Added by JERiveraMoya about 1 month ago. Updated about 7 hours ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2025-03-12
Due date:
% Done:

0%

Estimated time:

Description

Motivation

There is a couple of feature that can be covered in the same scenario.

  • Disk directly formatted (also called "using the whole disk) or in other words, without involving partitioning. We already covered this when we directly used physical volume but the other possibility is to format directly home.
  • Configure whether (and where, using an alias) Agama should calculate and create the extra partitions needed for booting.

We could combine both in single scenario with a profile which might look like this:

{
    "storage": {
        "drives": [
            {
                "search": "/dev/vda",
                "filesystem": {
                    "path": "/home"
                }
            },
            {
                "search": "/dev/vdb",
                "partitions": [
                    {
                        "filesystem": {
                            "path": "/"
                        }
                    }
                ]
            },
            {
                "search": "/dev/vdc",
                "alias": "boot-disk"
            }
        ],
        "boot": {
            "configure": "true",
            "device": "boot-disk"
        }
    }
}

I possible name could be this: sles_whole_disk_and_boot_unattended which is "almost" clear.

Acceptance criteria

  • AC1: Create new test suite to format directly home and configure boot partition in a different disk.
  • AC2: Validation should check that boot is really in a separate partition from root and that /home is not in any partition but in the disk itself.
Actions #1

Updated by JERiveraMoya about 1 month ago

  • Description updated (diff)
Actions #2

Updated by hjluo about 1 month ago

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

Updated by JERiveraMoya about 1 month ago

hjluo wrote in #note-3:

Draft without verification runs or validation do not make much sense, please use reporting wisely once you have achieve something that goes beyond the ticket specification.
Reason: to avoid look at something or trigger a review and finding nothing to do, I hope it is understandable.

Actions #5

Updated by hjluo about 1 month ago

- now the installation works but can't boot up, now trying to use bootindex=N for qume to see if it works.

Actions #6

Updated by hjluo 29 days ago

  • Now it works with UEFI and try to use templating for jsonnet and add validate_partition.
Actions #7

Updated by JERiveraMoya 20 days ago

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

Updated by JERiveraMoya 14 days ago

what setting did you use at the end?
could you please resume work in the PR to proceed with review? seems in WIP, not sure if there is any blocker.

Actions #9

Updated by hjluo 14 days ago · Edited

JERiveraMoya wrote in #note-8:

what setting did you use at the end?
could you please resume work in the PR to proceed with review? seems in WIP, not sure if there is any blocker.

Now use UEFI for boot from the boot disk and coding up for partition verificatin,I'd send out review again after run the VR. Thanks

Actions #10

Updated by hjluo 11 days ago

Can you please take a look at the updated PR#21442? thanks!

Actions #11

Updated by JERiveraMoya 9 days ago

  • Description updated (diff)
Actions #12

Updated by JERiveraMoya 7 days ago

Merged, let's do the setup.

Actions #13

Updated by hjluo 7 days ago

JERiveraMoya wrote in #note-12:

Merged, let's do the setup.

OK, so for the name should be sles_whole_disk_boot_unattended?

Actions #14

Updated by JERiveraMoya 7 days ago

hjluo wrote in #note-13:

JERiveraMoya wrote in #note-12:

Merged, let's do the setup.

OK, so for the name should be sles_whole_disk_boot_unattended?
Yes, would be descriptive.

Actions #15

Updated by hjluo 1 day ago

  • Added test case sles_whole_disk_boot_unattended in prod.
  • Added test case sles_whole_disk_boot_unattended in dev.
Actions #16

Updated by JERiveraMoya 1 day ago

Only missing point here is VR in prod/dev job groups.

Actions #17

Updated by hjluo 1 day ago

JERiveraMoya wrote in #note-16:

Only missing point here is VR in prod/dev job groups.

Yes, triggered and still scheduled, will check out tomorrow and update it. Thanks.

Actions #19

Updated by JERiveraMoya about 8 hours ago

hjluo wrote in #note-18:

Good, now you just need to the same in development. Please apply this for any ticket in the future, we always expect the jobs to pass in both groups unless some feature is not yet (ie in prod).
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=sles_whole_disk_boot_unattended&modules=&module_re=&group_glob=¬_group_glob=&comment=&distri=sle&version=agama-10.0&build=114.2&groupid=607#

Actions #21

Updated by JERiveraMoya about 7 hours ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF