https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-03-05T10:53:51ZopenSUSE Project Management ToolopenQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=1954462019-03-05T10:53:51Zokurzokurz@suse.com
<ul></ul><p>Comment from yosun:<br>
A yast problem block activate_kdump, yast2 kdump no longer exist. I'm writing a new function "activate_kdump_without_yast" in ./lib/kdump_utils.pm, could try to replace activate_kdump to activate_kdump_without_yast, after I finish my PR.</p>
openQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=1954492019-03-05T10:55:37Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/195449/diff?detail_id=193715">diff</a>)</li></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/15720">@yosun</a> I do not know how you came to the conclusion that yast2-kdump would not exist anymore because it is still there. I do not recommend to replace the existing functionality using the yast dialogs.</p>
openQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=1954552019-03-05T11:00:30Zyosunyosun@suse.com
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/15720">@yosun</a> I do not know how you came to the conclusion that yast2-kdump would not exist anymore because it is still there. I do not recommend to replace the existing functionality using the yast dialogs.</p>
</blockquote>
<p>Yeah, I found I was wrong, and I was willing to remove it to not confuse others, then I suddenly found the "remove" button :D</p>
<p>But FYI, I got a PR to enable kdump without yast. <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6959" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6959</a></p>
openQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=1955032019-03-05T11:26:14Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>[sle][functional][u] test fails in kdump_and_crash - apply workaround for x86_64 as well</i> to <i>[sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)</i></li><li><strong>Status</strong> changed from <i>Workable</i> to <i>Blocked</i></li><li><strong>Assignee</strong> changed from <i>zluo</i> to <i>okurz</i></li><li><strong>Target version</strong> changed from <i>Milestone 24</i> to <i>Milestone 25</i></li></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/21826">@zluo</a> sorry because the original ticket was originally deleted I do not know anymore why you are assigned. Unassigning. I set the "Blocker" flag on the bug <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1115946" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1115946</a> which is the one to use for x86_64, not the one mentioned in the description pointing to what looks like an aarch64 specific problem. In general I think a workaround would be a good idea though but not loosing the coverage of yast2 kdump.</p>
<p>For now blocked by the bug <a href="https://bugzilla.opensuse.org/show_bug.cgi?id=1115946" class="external">https://bugzilla.opensuse.org/show_bug.cgi?id=1115946</a></p>
openQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=2143792019-05-22T10:38:48Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> changed from <i>okurz</i> to <i>mgriessmeier</i></li></ul><p>Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.</p>
openQA Tests - action #48704: [sle][functional][u] test fails in kdump_and_crash - apply a workaround for x86_64 (as well)https://progress.opensuse.org/issues/48704?journal_id=2234842019-07-01T09:01:02Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>Resolved</i></li></ul><p>didn't happen for two month - I consider this fixed</p>