https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-11-26T12:15:40ZopenSUSE Project Management ToolopenQA Tests - action #80452: [qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**https://progress.opensuse.org/issues/80452?journal_id=3545502020-11-26T12:15:40Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/354550/diff?detail_id=351716">diff</a>)</li></ul> openQA Tests - action #80452: [qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**https://progress.opensuse.org/issues/80452?journal_id=3545522020-11-26T12:17:33Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/354552/diff?detail_id=351718">diff</a>)</li></ul> openQA Tests - action #80452: [qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**https://progress.opensuse.org/issues/80452?journal_id=3546682020-11-26T12:55:23Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> openQA Tests - action #80452: [qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**https://progress.opensuse.org/issues/80452?journal_id=3546822020-11-26T13:07:12Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Category</strong> set to <i>Bugs in existing tests</i></li></ul> openQA Tests - action #80452: [qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**https://progress.opensuse.org/issues/80452?journal_id=3568802020-12-08T10:49:46Zgeorggkioulis@suse.com
<ul><li><strong>Subject</strong> changed from <i>[qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests</i> to <i>[qe-core][qem] Problems with aarch64 RAID 15SP1/SP2 QU tests - **Suggested Backport**</i></li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Some reneedling was required; The aarch64 RAID jobs of 15SP1 and 15SP2 QUs should be passing consistently now.</p>
<p>Concerning the irregular <code>reconnect_mgmt_console</code> failure, this issue is actually caused in <code>await_install</code>.<br>
The reboot message at the end of the installation has a default timeout of 10 seconds.<br>
In some archs like aarch64 and s390, it happens that await_install module's needle check is not catching up with the 10 second timeout, and reboot is not cancelled.<br>
This results in the machine rebooting when it should not, and failing in the next module, <code>reconnect_mgmt_console</code>.</p>
<p>In order to fix this issue, <a href="https://github.com/yast/yast-yast2/pull/977/files" class="external">PR_1</a> and <a href="https://github.com/yast/yast-installation/pull/823/files" class="external">PR2</a> were introduced. <br>
This allows for the following usage, as seen in <code>lib/bootloader_setup.pm</code>:<br>
<code>push @params, 'reboot_timeout=' . get_var('REBOOT_TIMEOUT', 0) unless (is_leap('<15.2') || is_sle('<15-SP2'));</code></p>
<p>The above line, by default, pushes in the list of bootparams the <code>reboot_timeout=0</code> which, for 15-SP2 that contains the two aforementioned PR changes, removes the timeout on the reboot message and openQA will have time to catch up.</p>
<p>However, in 15-SP1 this boot parameter is not checked, so there is no straightforward way of changing or disabling the timeout. <br>
The suggested approach here is to request a backport of this for yast in SLE 15-SP1.</p>
<p>Since it is not likely that there will ever be a new 15-SP1 QU release, the backport approach remains a suggestion for now.</p>