https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-03-31T11:14:03ZopenSUSE Project Management ToolopenQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5069272022-03-31T11:14:03Zosukup
<ul><li><strong>Project</strong> changed from <i>QA</i> to <i>openQA Project</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5069302022-03-31T11:18:59Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Regressions/Crashes</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5071552022-04-01T09:10:19Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/507155/diff?detail_id=479360">diff</a>)</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5083892022-04-06T09:29:14Zosukup
<ul></ul><p>reported also as <a href="https://github.com/openSUSE/qem-dashboard/issues/61" class="external">https://github.com/openSUSE/qem-dashboard/issues/61</a> </p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5083922022-04-06T09:46:13Zosukup
<ul></ul><p>Problem here is cased by using INCIDENT as common identificator. Unfortunately this is sometimes reused.</p>
<p>We use INCIDENT because we schedule jobs in Testing queue with RRiD ( SUSE:Maintenace:INCIDENT:ReviewRequest ) and also Staging queue which haven't ReviewRequest ( SUSE:Maintenance:INCIDENT ) and we want tests in staging to be valid also after RR is created and incident is moved to testing queue. </p>
<ul>
<li>most proper solution will be create new identifier</li>
<li>simple workaround - automatic data deletion based on age of data ( +- results older than month in aggregates are useless and can cause this problem)</li>
</ul>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5084102022-04-06T10:22:59Zosukup
<ul></ul><p>we have timestamp in results ... so we can pretty simply create cron job which cleanup results :D</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5088392022-04-07T10:10:41Zlivdywanliv.dywan@suse.com
<ul><li><strong>Subject</strong> changed from <i>qem-bot/dashboard - mixed old and new incidents</i> to <i>qem-bot/dashboard - mixed old and new incidents size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/508839/diff?detail_id=480786">diff</a>)</li><li><strong>Category</strong> changed from <i>Regressions/Crashes</i> to <i>Support</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5088422022-04-07T10:11:13Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5088572022-04-07T10:28:32Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2022-04-22</i></li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>I asked in <a href="https://suse.slack.com/archives/C02CCRM8946/p1649327149714419" class="external">https://suse.slack.com/archives/C02CCRM8946/p1649327149714419</a></p>
<blockquote>
<p>Hi, I have a question regarding submissions for incidents which kinda "reuse" old incident numbers, see <a href="https://progress.opensuse.org/issues/109310" class="external">https://progress.opensuse.org/issues/109310</a> for details about the problem that this brings. Does anyone have objections (and suggestions) if we (automatically) reject submissions for old incidents that existed in before? The effect would be that anyone creating new submissions would need to start new incidents (I hope I got the terms right here)</p>
</blockquote>
<p>If there is no objection until 2022-04-22 then I suggest we ask openQA test reviewers to reject according submissions and look into automatic rejection.</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5088842022-04-07T11:17:21Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>qem-bot/dashboard - mixed old and new incidents size:M</i> to <i>qem-bot/dashboard - mixed old and new incidents</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/508884/diff?detail_id=480858">diff</a>)</li><li><strong>Due date</strong> deleted (<del><i>2022-04-22</i></del>)</li><li><strong>Category</strong> changed from <i>Support</i> to <i>Feature requests</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>I asked maintenance experts in <a href="https://suse.slack.com/archives/C02CCRM8946/p1649327149714419">https://suse.slack.com/archives/C02CCRM8946/p1649327149714419</a> if they are ok if we reject such submissions and ask for resubmission as new incidents with a unique number. And with me stating the "harshest" option first I could spawn some quite helpful answers :)</p>
<blockquote>
<p>Hi, I have a question regarding submissions for incidents which kinda "reuse" old incident numbers, see <a href="https://progress.opensuse.org/issues/109310">https://progress.opensuse.org/issues/109310</a> for details about the problem that this brings. Does anyone have objections (and suggestions) if we (automatically) reject submissions for old incidents that existed in before? The effect would be that anyone creating new submissions would need to start new incidents (I hope I got the terms right here)</p>
</blockquote>
<p>Marina Latini and Simon Lees explaining when an incident is re-used:</p>
<blockquote>
<p>Marina Latini: we are "reusing" old incidents only if really needed. we don't really use old parked incidents randomly. what you call reuse can be an incident with several resubmissions and where we had an initial declined/revoked RR for example.<br>
we have also the case of re-releases of already released incidents and for those it's really wrong to create a new incident.<br>
Simon Lees: the main place i've used them is if we release say SLE-15-SP3 with a regression but havent released for older codestreams then generally we will fix the regression in the older codestreams in the original incident rather then creating a new one (obviously for streams that are released we create a new one)</p>
</blockquote>
<p>Oliver Kurz and Stephan Kulow: explaining that the impact of the issue is low so far:</p>
<blockquote>
<p>Oliver Kurz: ok, I will see what we can do. @Stephan Kulow can you say why are we running into that problem reported now? I don't think that this is a change in maintenance processes. So it's either that qem-bot introduced a regression vs. older tooling or people have ignored the missing support for months/years<br>
Stephan Kulow: As Marina mentioned, it's not done often - and we had this case in the past. But @Jozef Pupava just ignored old results (or they passed and there was nothing to ignore)</p>
</blockquote>
<p>My suggestion and from Stephan Kulow:</p>
<blockquote>
<p>Oliver Kurz: ok, so both you would say that incident_id+release_request_id should be enough to make it unique?<br>
Stephan Kulow: The bot very well knows that the incident is bound to which RR - and if the RR changes, it needs to delete/invalidate the old data</p>
</blockquote>
<p>So my open question: How easy would it be to implement that suggestion and where to start?</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5089232022-04-07T12:21:42Zcoolocoolo@suse.com
<ul></ul><p>the dashboard can trigger that cleanup when it gets new swamp data and notices an update of the RR.</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5089412022-04-07T12:52:05Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" href="/issues/103701">action #103701</a>: Resubmited incident (ID) with new release request (RR) inherits incident test results from previous RR</i> added</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5089772022-04-07T13:55:15Zokurzokurz@suse.com
<ul></ul><p>I see that there was already an attempt which looks like it intended to address the same issue: <a href="https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/46/diffs#14610756e1f5900260e8e8ecf7249d18a0fc7a5c_74_76" class="external">https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/46/diffs#14610756e1f5900260e8e8ecf7249d18a0fc7a5c_74_76</a></p>
<p>coolo wrote:</p>
<blockquote>
<p>the dashboard can trigger that cleanup when it gets new swamp data and notices an update of the RR.</p>
</blockquote>
<p>ok, sounds good.</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5090522022-04-07T14:08:19Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> set to <i>#109641</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5114162022-04-14T10:22:46Zokurzokurz@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-1 priority-3 priority-lowest child" href="/issues/109974">action #109974</a>: qem-bot/dashboard - mixed old and new incidents - potential future ideas</i> added</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5114222022-04-14T10:23:54Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>qem-bot/dashboard - mixed old and new incidents</i> to <i>qem-bot/dashboard - mixed old and new incidents size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/511422/diff?detail_id=483228">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5114232022-04-14T10:28:44Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/511423/diff?detail_id=483232">diff</a>)</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5114252022-04-14T10:30:55Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/511425/diff?detail_id=483234">diff</a>)</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5118702022-04-19T09:19:59Zosukup
<ul></ul><p>it can be shortened to 2x DELETE queries:</p>
<pre><code>DELETE FROM update_openqa_settings WHERE id IN (SELECT update_settings FROM openqa_jobs WHERE update_settings is not NULL AND updated < NOW() - INTERVAL '90 days');
DELETE FROM openqa_jobs WHERE update_settings is not NULL AND updated < NOW() - INTERVAL '90 days')
</code></pre> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5118732022-04-19T09:25:28Zosukup
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>osukup</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5126832022-04-21T16:40:51Zkraihsebastian.riedel@suse.com
<ul></ul><p>Opened a PR: <a href="https://github.com/openSUSE/qem-dashboard/pull/63" class="external">https://github.com/openSUSE/qem-dashboard/pull/63</a></p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5128902022-04-22T09:14:53Zkraihsebastian.riedel@suse.com
<ul><li><strong>Assignee</strong> changed from <i>osukup</i> to <i>kraih</i></li></ul><p>Stealing this ticket from Ondrej to keep an eye on it, since the proposed PR is now being deployed.</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5128932022-04-22T09:16:09Zosukup
<ul></ul><p>kraih wrote:</p>
<blockquote>
<p>Stealing this ticket from Ondrej to keep an eye on it, since the proposed PR is now being deployed.</p>
</blockquote>
<p>one minute before mine action to forward to you and setting to feedback. Your solution is beautiful</p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5129922022-04-22T14:50:54Zkraihsebastian.riedel@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5144192022-04-28T13:20:43Zkraihsebastian.riedel@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed child" href="/issues/110409">action #110409</a>: qem-dashboard - remove old openQA jobs when rr_number changes size:M</i> added</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5144282022-04-28T13:23:30Zkraihsebastian.riedel@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>I think this ticket is resolved, but there is more work to be done, so i've made a followup ticket with more cleanup requirements that have come up in the meantime. <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: qem-dashboard - remove old openQA jobs when rr_number changes size:M (Resolved)" href="https://progress.opensuse.org/issues/110409">#110409</a></p>
openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=5437732022-08-05T16:21:14Zjbaier_czjbaier@suse.cz
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" href="/issues/114694">action #114694</a>: Incident seems to have missing aggregate test results in qem-dashboard but openQA jobs exists size:M</i> added</li></ul> openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:Mhttps://progress.opensuse.org/issues/109310?journal_id=7618992024-02-08T12:43:28Zjbaier_czjbaier@suse.cz
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-4 priority-default" href="/issues/155206">action #155206</a>: [qem-bot] re-release update can miss repo and thus not schedule updates</i> added</li></ul>