https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842020-10-13T10:49:14ZopenSUSE Project Management ToolopenQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3355752020-10-13T10:49:14Zokurzokurz@suse.com
<ul><li><strong>Copied from</strong> <i><a class="issue tracker-4 status-12 priority-3 priority-lowest child" href="/issues/73282">action #73282</a>: auto_review:"setup failure: Cache service status error from API: Minion job.*Worker went away":retry</i> added</li></ul> openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3355782020-10-13T10:49:39Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/335578/diff?detail_id=330520">diff</a>)</li></ul> openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3365832020-10-16T15:13:20Zkraihsebastian.riedel@suse.com
<ul></ul><p>This one is not so harmless. The error message <code>Job terminated unexpectedly (exit code: 2, signal: 0)</code> comes directly from the Minion job queue worker, and means that the process spawned for the download has died unexpectedly. This is very unusual, there is nothing that would make a Minion job process exit with the status code 2 on its own. Normal exceptions would get caught and result in a real exception message as the job result. This is the fallback for a fallback triggering.</p>
openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3368892020-10-18T12:54:24Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3539342020-11-25T11:58:44Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> set to <i>#62420</i></li></ul> openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=3851052021-02-23T14:57:43Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul><p>The main reason I kept this ticket on the backlog was <a class="issue tracker-4 status-12 priority-3 priority-lowest child" title="action: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexp... (Workable)" href="https://progress.opensuse.org/issues/73288#note-3">#73288#note-3</a> but with no action here and the good workaround with automatic retry in place I think we can live with the current state for the time being.</p>
openQA Project - action #73288: auto_review:"setup failure: Cache service status error from API: Minion job.*Job terminated unexpectedly":retryhttps://progress.opensuse.org/issues/73288?journal_id=4670792021-11-23T22:19:15Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> changed from <i>#62420</i> to <i>#102909</i></li></ul>