https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-08-02T13:34:48ZopenSUSE Project Management ToolopenQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2322502019-08-02T13:34:48Zybonatakisioannis.bonatakis@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed behind-schedule" href="/issues/49010">action #49010</a>: [opensuse][functional][y] Add test suite for NET install + expert partitioner on Tumbleweed</i> added</li></ul> openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2322742019-08-02T13:50:14Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/232274/diff?detail_id=228887">diff</a>)</li></ul> openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2322832019-08-02T14:23:12Zokurzokurz@suse.com
<ul></ul><p>first checking if I can run tests on o3 with explicitly specified code and vars files:</p>
<pre><code>for i in 997893 997802 997878; do openqa-clone-job --within-instance https://openqa.opensuse.org --skip-chained-deps $i UEFI=1 UEFI_PFLASH= BIOS= UEFI_PFLASH_CODE=/usr/share/qemu/ovmf-x86_64-ms-code.bin UEFI_PFLASH_VARS=/usr/share/qemu/ovmf-x86_64-ms-vars.bin _GROUP=0 TEST=okurz_uefi_code_vars_poo55052 BUILD=okurz_poo55052; done
</code></pre>
<p>Created job #998609: opensuse-Tumbleweed-DVD-x86_64-Build20190801-uefi@64bit -> <a href="https://openqa.opensuse.org/t998609" class="external">https://openqa.opensuse.org/t998609</a><br>
Created job #998610: opensuse-Tumbleweed-NET-x86_64-Build20190801-uefi@64bit -> <a href="https://openqa.opensuse.org/t998610" class="external">https://openqa.opensuse.org/t998610</a><br>
Created job #998611: opensuse-Tumbleweed-DVD-x86_64-Build20190801-uefi@USBboot_64 -> <a href="https://openqa.opensuse.org/t998611" class="external">https://openqa.opensuse.org/t998611</a></p>
<p>Need to check results later. In the code we have hardcoded lookup paths for the firmware files, e.g. '/usr/share/qemu/ovmf-x86_64-ms.bin' . The other paths for fedora and Debian look like they already reference the "code" firmware already, e.g. '/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd' . I wonder if we actually still need to support the pflash mode or can just say that UEFI requires code and vars. For convience we should look the firmware files still up though.</p>
<p>Also, our tests os-autoinst-distri-opensuse set UEFI_PFLASH for all except aarch64 which already explicitly select firmware files. I wonder if we can simply lookup the correct code/vars files and get rid of UEFI_PFLASH in the test code to use that mode.</p>
<p>EDIT: All three tests worked the same as the ones for production tests using UEFI_PFLASH hardcoded.</p>
openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2322862019-08-02T14:43:45Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p><a href="https://github.com/os-autoinst/os-autoinst/pull/1190" class="external">https://github.com/os-autoinst/os-autoinst/pull/1190</a></p>
<p>after that should apply the change for os-autoinst-distri-opensuse to remove UEFI_PFLASH</p>
openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2328052019-08-06T13:11:01Zokurzokurz@suse.com
<ul></ul><p>merged. <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8124" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8124</a> for the tests adaption which we should do only after rolling out the changes to both o3 and osd.</p>
openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2329882019-08-07T08:36:18Zokurzokurz@suse.com
<ul></ul><p>hm, I thought we could have os-autoinst bring in the new support while working with old test code but apparently this did not work out as expected as all the UEFI tests on o3 broke since today's nightly os-autoinst update. <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8124" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8124</a> merged and I will retrigger according tests. Test code is deployed to o3, retriggered all uefi incompletes I could find on <a href="https://openqa.opensuse.org/tests/?&resultfilter=Incomplete" class="external">https://openqa.opensuse.org/tests/?&resultfilter=Incomplete</a> . Monitoring <br>
<a href="https://openqa.opensuse.org/tests/1000511#live" class="external">https://openqa.opensuse.org/tests/1000511#live</a> , passed disk_boot of installed system. ended successfully now. Let's monitor this on OSD later then.</p>
openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2332102019-08-07T11:34:31Zokurzokurz@suse.com
<ul></ul><p><a href="https://openqa.suse.de/tests/3221296#" class="external">https://openqa.suse.de/tests/3221296#</a> seems to be fine as well.</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/32492">@ybonatakis</a> please test again on current Tumbleweed. It looks fine to me. I would be interested to hear from you it still does not work for you on current Tumbleweed with most recent os-autoinst+os-autoinst-distri-opensuse</p>
openQA Project - action #55052: Support for ovmf => 2019 or "current Tumbleweed can not execute UEFI tests anymore"https://progress.opensuse.org/issues/55052?journal_id=2364022019-08-19T14:14:38Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>seems to be fine</p>