https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-03-27T07:28:32ZopenSUSE Project Management ToolopenQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2023402019-03-27T07:28:32ZSLindoMansillaslindomansilla@suse.com
<ul><li><strong>Subject</strong> changed from <i>test fails in validate_lvm_encrypt finding boot partition in aarch64</i> to <i>[functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64</i></li></ul><p>As a result of backlog triaging (see <a href="https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging" class="external">https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging</a> for more information).</p>
<p>Please, feel free to adjust the category or the "[label]" if you think different.</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2023552019-03-27T07:36:58ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>Thanks! I forgot totally labels for a moment :)</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2025352019-03-27T09:28:52Zriafarov
<ul><li><strong>Target version</strong> set to <i>Milestone 24</i></li></ul> openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2025382019-03-27T09:29:15Zriafarov
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>Increasing priority as is a recent regression.</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2026102019-03-27T10:04:40Zriafarov
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/202610/diff?detail_id=200603">diff</a>)</li><li><strong>Estimated time</strong> set to <i>3.00 h</i></li></ul> openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2026372019-03-27T10:27:22Zriafarov
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2038162019-04-02T11:51:59ZJRivrainjrivrain@suse.com
<ul><li><strong>Assignee</strong> set to <i>JRivrain</i></li></ul> openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2038852019-04-02T16:38:36ZJRivrainjrivrain@suse.com
<ul></ul><p>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.<br>
temporary PR <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7194" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7194</a></p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2038882019-04-02T16:42:05ZJRivrainjrivrain@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2042062019-04-03T17:59:07ZJRivrainjrivrain@suse.com
<ul></ul><p>So, create_new_partition_table in partition_setup.pm does this:</p>
<pre><code>my ($table_type) = shift // (is_storage_ng) ? 'GPT' : 'MSDOS';
</code></pre>
<p>So it will create a MSDOS partition if we are not using storage_ng (eg on sle12)<br>
But later in the function:</p>
<pre><code>if (!get_var('UEFI') && !check_var('BACKEND', 's390x') || is_storage_ng)
[choose GPT or MSDOS, set size...]
</code></pre>
<p>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. </p>
<p>Sle12 does not create a /boot/grub2/(arch)-efi <a href="https://openqa.suse.de/tests/2770373#step/validate_lvm_encrypt/116" class="external">btrfs subvolume</a> if there is an EFI partition (but it does if there is <a href="https://openqa.suse.de/tests/2739724#step/validate_lvm_encrypt/116" class="external">no efi partition</a>) and this causes the test to fail. sle15 creates a /boot/grub2/(arch)-efi <a href="https://openqa.suse.de/tests/2766569#step/validate_lvm_encrypt/129" class="external">subvolume</a>, and also creates a <a href="https://openqa.suse.de/tests/2773116#step/partitioning_full_lvm/74" class="external">2M "bios" partition</a> that does not get mounted.</p>
<p>EDIT: sle12 on x86_64 does create a boot subvolume: <a href="http://eris.suse.cz/tests/13030#step/partitioning_full_lvm/62" class="external">http://eris.suse.cz/tests/13030#step/partitioning_full_lvm/62</a> (thanks Martin for the VR). So That is probably a bug. </p>
<p>**Remark: sle12 with UEFI probably boots using <a href="https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#CSM_booting" class="external">CSM</a>, because AFAIK, UEFI needs a separate EFI partition to work properly. If I'm right, this makes the <a href="https://fate.suse.com/320215" class="external">fate test case</a> more or less invalid.</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2045722019-04-05T11:39:58ZJRivrainjrivrain@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><blockquote>
<p>EDIT: sle12 on x86_64 does create a boot subvolume: <a href="http://eris.suse.cz/tests/13030#step/partitioning_full_lvm/62" class="external">http://eris.suse.cz/tests/13030#step/partitioning_full_lvm/62</a> (thanks Martin for the VR). So That is probably a bug. </p>
</blockquote>
<p>The devs do not consider this as a bug, so let's just work around it. I removed [WIP] from the <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/7194" class="external">PR</a></p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2051782019-04-09T09:05:09Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-04-09</i> to <i>2019-04-23</i></li></ul><p>VR on osd is missing.</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2064232019-04-15T08:51:24Zriafarov
<ul></ul><p>No deployment yet: <a href="https://confluence.suse.de/pages/viewpage.action?pageId=194052156" class="external">https://confluence.suse.de/pages/viewpage.action?pageId=194052156</a></p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2075032019-04-23T08:33:32Zriafarov
<ul></ul><p>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.</p>
openQA Tests - action #49718: [functional][y] test fails in validate_lvm_encrypt finding boot partition in aarch64https://progress.opensuse.org/issues/49718?journal_id=2075212019-04-23T08:40:21Zriafarov
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>