https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-09-19T13:31:45ZopenSUSE Project Management ToolopenQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5547942022-09-19T13:31:45Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul> openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5547972022-09-19T13:35:41Zokurzokurz@suse.com
<ul></ul><p>I found that <code>systemctl --failed</code> lists var-lib-openqa-share.mount, maybe related. <a href="https://openqa.opensuse.org/admin/workers/413" class="external">openqaworker1_container:101</a> shows that the latest openQA jobs ran 3 days ago, on 2022-09-16. registry.opensuse.org/devel/openqa/containers15.2/openqa_worker:latest is certainly outdated and we should try to run a 15.4 or Tumbleweed version. Please update our upgrade instructions for workers accordingly to include that step for the next time.</p>
<p>Instructions for the setup can be found on <a href="https://progress.opensuse.org/projects/openqav3/wiki/Wiki#o3-s390-workers" class="external">https://progress.opensuse.org/projects/openqav3/wiki/Wiki#o3-s390-workers</a></p>
<p>The original setup ticket was <a class="issue tracker-4 status-3 priority-5 priority-high3 closed" title="action: replacement setup for o3 s390x openQA workers size:M (Resolved)" href="https://progress.opensuse.org/issues/97751">#97751</a></p>
openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5548032022-09-19T13:36:53Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed" href="/issues/97751">action #97751</a>: replacement setup for o3 s390x openQA workers size:M</i> added</li></ul> openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5548062022-09-19T13:37:53Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/554806/diff?detail_id=523288">diff</a>)</li><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5548452022-09-19T14:32:47Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul> openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5548482022-09-19T14:57:14Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>Re-conducted steps on <a href="https://progress.opensuse.org/projects/openqav3/wiki/Wiki#o3-s390-workers" class="external">https://progress.opensuse.org/projects/openqav3/wiki/Wiki#o3-s390-workers</a>. I tried <code>registry.opensuse.org/devel/openqa/containers15.4/openqa_worker:latest</code> instead of <code>registry.opensuse.org/devel/openqa/containers15.2/openqa_worker:latest</code> but it looks like the containers are still on 15.2.. For today I'll keep it that way to process pending s390x jobs (which so far look good).</p>
openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5550102022-09-20T05:21:28Zopenqa_reviewopenqa-review@suse.de
<ul><li><strong>Due date</strong> set to <i>2022-10-04</i></li></ul><p>Setting due date based on mean cycle time of SUSE QE Tools</p>
openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5551752022-09-20T09:52:54Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>Recovered the setup and updated the setup to use 15.4 (see updated instructions in Wiki).</p>
<p>Not all jobs are passing but these failures were there before and are likely caused by something on the remote work. It generally works on the updated container, e.g. <a href="https://openqa.opensuse.org/tests/2704235" class="external">https://openqa.opensuse.org/tests/2704235</a>.</p>
openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5558112022-09-21T15:31:01Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>I guess that can be considered resolved. Some s390x jobs are passing, some are failing (like before) but they are executed again.</p>
openQA Infrastructure - action #116782: o3 s390 workers are offlinehttps://progress.opensuse.org/issues/116782?journal_id=5699652022-11-02T11:04:19Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-6 priority-high2 closed" href="/issues/119713">action #119713</a>: Leap tests are failing because of failed log file uploading in multiple tests on s390x size:M</i> added</li></ul>