QA » openQA Project » openQA Tests

Thanks! I forgot totally labels for a moment :)

On sle12+aarch64, the boot partition is separated. I did a change but I think the lvm-full-encrypt should in fact be excluded for this case, since it is actually doing the same as lvm-encrypt-separate-boot. It seems to be set by the partitioner itself.
temporary PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7194

So, create_new_partition_table in partition_setup.pm does this:

my ($table_type) = shift // (is_storage_ng) ? 'GPT' : 'MSDOS';

So it will create a MSDOS partition if we are not using storage_ng (eg on sle12)
But later in the function:

if (!get_var('UEFI') && !check_var('BACKEND', 's390x') || is_storage_ng) 
[choose GPT or MSDOS, set size...]

For sle 12 on aarch64, the installer does not propose MSDOS as partition table as UEFI si set, so only in that case we have GPT partition table and /boot/efi on a separate vfat partition.

Sle12 does not create a /boot/grub2/(arch)-efi btrfs subvolume if there is an EFI partition (but it does if there is no efi partition) and this causes the test to fail. sle15 creates a /boot/grub2/(arch)-efi subvolume, and also creates a 2M "bios" partition that does not get mounted.

EDIT: sle12 on x86_64 does create a boot subvolume: http://eris.suse.cz/tests/13030#step/partitioning_full_lvm/62 (thanks Martin for the VR). So That is probably a bug.

**Remark: sle12 with UEFI probably boots using CSM, because AFAIK, UEFI needs a separate EFI partition to work properly. If I'm right, this makes the fate test case more or less invalid.

No deployment yet: https://confluence.suse.de/pages/viewpage.action?pageId=194052156

We have a bug on arm, which blocks execution of the test module. So let's resolve and act on the issues step by step.