https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-03-17T05:59:26ZopenSUSE Project Management Toolqe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6144412023-03-17T05:59:26ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Tests</i> to <i>qe-yam</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/614441/diff?detail_id=577049">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li><li><strong>Target version</strong> set to <i>Current</i></li><li><strong>Parent task</strong> set to <i>#121876</i></li></ul> qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6144442023-03-17T06:00:21ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Subject</strong> changed from <i>test fails in bootloader_start for ipmi woker</i> to <i>test fails in bootloader_start for ipmi worker</i></li></ul> qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6144502023-03-17T06:45:30Zhjluohluo@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>hjluo</i></li></ul> qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6144622023-03-17T07:56:49Zhjluohluo@suse.com
<ul></ul><p>try scoot:<br>
<a href="https://openqa.suse.de/t10730536" class="external">https://openqa.suse.de/t10730536</a><br>
<a href="https://openqa.suse.de/t10730537" class="external">https://openqa.suse.de/t10730537</a></p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6148402023-03-20T05:49:02Zhjluohluo@suse.com
<ul></ul><p>now passed in 81.1 with grenache-1:16<br>
<a href="https://openqa.suse.de/tests/10675807#settings" class="external">https://openqa.suse.de/tests/10675807#settings</a></p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6150142023-03-20T10:05:30ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>hjluo</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> deleted (<del><i>Current</i></del>)</li></ul><p>Thanks for checking it.<br>
Moving back to backlog, we might need this in future, I don't know how stable is to use that worker.</p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6264502023-04-22T00:37:45Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: fips_ker_mode_tests_crypt_web_intel_ipmi@64bit-ipmi<br>
<a href="https://openqa.suse.de/tests/10954413#step/bootloader_start/1" class="external">https://openqa.suse.de/tests/10954413#step/bootloader_start/1</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6292252023-05-04T04:38:20ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>syrianidou_sofia</i></li><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li><li><strong>Target version</strong> set to <i>Current</i></li></ul><p>MR: <a href="https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/502" class="external">https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/502</a></p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6292282023-05-04T04:45:08ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>@ssrianidou, could you please isos post?<br>
we might be missing some param in <a href="https://openqa.suse.de/tests/11025375" class="external">https://openqa.suse.de/tests/11025375</a><br>
perhaps once merged is a bit easier, otherwise we need to check settings for passing jobs with this worker.</p>
qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6292312023-05-04T04:45:44ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Subject</strong> changed from <i>test fails in bootloader_start for ipmi worker</i> to <i>Try out different ipmi machine in Yam job group</i></li></ul> qe-yam - action #126143: Try out different ipmi machine in Yam job grouphttps://progress.opensuse.org/issues/126143?journal_id=6317872023-05-10T09:14:29Zsyrianidou_sofiasofia.syrianidou@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Under settings option MACHINE=64bit-ipmi-large-mem we have high failure rate due to pxeboot graphics problem: <a href="https://openqa.suse.de/tests/11051161#step/bootloader_start/8" class="external">https://openqa.suse.de/tests/11051161#step/bootloader_start/8</a><br>
on grenache-1:10 and some repository issue on grenache-1:17 : <a href="https://openqa.suse.de/tests/11043804#step/bootloader_start/10" class="external">https://openqa.suse.de/tests/11043804#step/bootloader_start/10</a><br>
Contacting the virtualization team here : <a href="https://suse.slack.com/archives/C02CGKV748P/p1683205911080479" class="external">https://suse.slack.com/archives/C02CGKV748P/p1683205911080479</a> didn't provide a solution, usable on osd.<br>
There are two additional options for ipmi machine, 64bit-ipmi-nvdimm that exists only on grenache-1:11 which has a high success rate, so changing our test setting to MACHINE=virt-mm-64bit-ipmi would ensure that the test runs on worker grenache-1:11 but would probably take longer time to schedule. Another option is MACHINE=virt-mm-64bit-ipmi that exists in 8 workers and none seem to constantly fail.</p>
<p>VRs for virt-mm-64bit-ipmi:<br>
<a href="https://openqa.suse.de/tests/11084215" class="external">https://openqa.suse.de/tests/11084215</a><br>
<a href="https://openqa.suse.de/tests/11084202" class="external">https://openqa.suse.de/tests/11084202</a></p>
<p><a href="https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/503" class="external">https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/503</a></p>