https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-09-13T09:42:27ZopenSUSE Project Management ToolopenQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4452812021-09-13T09:42:27ZMDouchamartin.doucha@suse.com
<ul></ul><p>The most common s390x worker error is failure to execute <code>define_and_start()</code> in <code>bootloader_zkvm</code>. But this failure has multiple different causes:</p>
<ul>
<li>Memory allocation issue: <a href="https://openqa.suse.de/tests/6044126#step/bootloader_zkvm/28" class="external">https://openqa.suse.de/tests/6044126#step/bootloader_zkvm/28</a></li>
<li><code>macvtap</code> address collision: <a href="https://openqa.suse.de/tests/6926261#step/bootloader_zkvm/28" class="external">https://openqa.suse.de/tests/6926261#step/bootloader_zkvm/28</a></li>
<li>Netlink connection error: <a href="https://openqa.suse.de/tests/7085075#step/bootloader_zkvm/28" class="external">https://openqa.suse.de/tests/7085075#step/bootloader_zkvm/28</a></li>
</ul>
<p>Some happen randomly due to worker overload, others are the result of manual misconfiguration and persist on one or more worker slots until manually fixed.</p>
openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4458782021-09-15T05:53:06Zpcervinkapcervinka@suse.com
<ul><li><strong>Project</strong> changed from <i>178</i> to <i>175</i></li></ul> openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4460732021-09-15T08:28:39Zszarate
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed" href="/issues/97532">action #97532</a>: [qe-core][sporadic] s390x jobs are failing to boot auto_review:"error: Cannot set interface flags on 'macvtap.*': Address already in use":retry</i> added</li></ul> openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4460822021-09-15T08:34:22Zszarate
<ul></ul><p>Hi Petr, In any case if you're struggling to figure out the root cause of those problems, you can ping me directly, or mention the issue in the qe-core/eng-testing channels, but as I mentioned during the call.</p>
<p>I suspect that the memory one (if it happens again lmk) could be related to too many jobs running on the same machine.</p>
openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4461122021-09-15T09:00:00Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>175</i> to <i>openQA Tests</i></li><li><strong>Subject</strong> changed from <i>Steps in case of s390 failures</i> to <i>[qe-core][kernel] Steps in case of s390 failures</i></li><li><strong>Category</strong> set to <i>Bugs in existing tests</i></li></ul><p>discussed in weekly QE sync 2021-09-15. <a class="user active user-mention" href="https://progress.opensuse.org/users/23010">@szarate</a> already linked the important related ticket <a class="issue tracker-4 status-3 priority-5 priority-high3 closed" title="action: [qe-core][sporadic] s390x jobs are failing to boot auto_review:"error: Cannot set interface flags... (Resolved)" href="https://progress.opensuse.org/issues/97532">#97532</a> . The above mentioned test modules mention mgriessmeier as maintainer hence I added him as watcher to the ticket. He might be able to help. If not then I see the responsibility on the QE Core team about these s390x particularities. In case of issues which look not specific to the test code of os-autoinst-distri-opensuse then tools team is responsible. All tools team members are expected to be responsive in chat (<a href="https://progress.opensuse.org/projects/qa/wiki#Common-tasks-for-team-members" class="external">https://progress.opensuse.org/projects/qa/wiki#Common-tasks-for-team-members</a>) , e.g. #eng-testing of the internal chat, so questions can be raised there. With this I think we can move the ticket out of "qam-qasle-collaboration" into the "openQA Tests" project with according keywords</p>
openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=4885832022-02-09T08:03:24Ztjyrinki_susetjyrinki+redmine@suse.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-12 priority-4 priority-default" href="/issues/105049">action #105049</a>: [qe-core] System cannot boot after installation in s390x in multiple test suites</i> added</li></ul> openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=5533932022-09-15T02:44:38Zslo-gin
<ul></ul><p>This ticket was set to <strong>Normal</strong> priority but was not updated <a href="https://progress.opensuse.org/projects/openqatests/wiki#SLOs-service-level-objectives" class="external">within the SLO period</a>. Please consider picking up this ticket or just set the ticket to the next lower priority.</p>
openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=5831772022-12-09T13:43:36Zokurzokurz@suse.com
<ul><li><strong>Tags</strong> changed from <i>s390, openQA, infrastructure</i> to <i>s390, openQA, infra</i></li></ul> openQA Tests - action #98541: [qe-core][kernel] Steps in case of s390 failureshttps://progress.opensuse.org/issues/98541?journal_id=5844012022-12-13T06:27:31Zpcervinkapcervinka@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul>