Actions
action #30274
closedisos post sometimes trigger iso_cancel for whole product
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2018-01-12
Due date:
% Done:
0%
Estimated time:
Description
this event was not directly triggered
https://openqa.suse.de/admin/auditlog?eventid=928340
most probably it is consequence of doing isos post
So, when I did following call:
client isos post ARCH=x86_64 DISTRI=sle FLAVOR=Installer-DVD VERSION=15 ISO=SLE-15-Installer-DVD-x86_64-Build418.3-Media1.iso BUILD=418.3 TEST=autoyast_multipath --host https://openqa.suse.de
In the audit logs of openQA I got an entry with my name:
7 minutes ago riafarov iso_cancel { "VERSION": "15", "FLAVOR": "Installer-DVD", "ARCH": "x86_64", "DISTRI": "sle" }
Even though I haven't called cancel explicitly. So, it looks like client wanted to obsolete the run, but instead of single test suite, it has canceled all of them for defined medium.
As a workaround one can use _NOOBSOLETEBUILD=1 option not to obsolete jobs, which should help.
Actions