⚲

Project

General

Profile

Home
Projects
Help

Search:

All Projects

QA

Overview
Activity
Roadmap
Issues
Gantt
Calendar
Wiki

Custom queries

may-sprint
new immediate tickets
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - triage: untriaged issues
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #113345

closed

qem-bot does not ignore Development/Leap job groups as it should size:M

Added by mgrifalconi almost 2 years ago. Updated almost 2 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

okurz

Target version:

openQA Project - Ready

Start date:

Due date:

% Done:

Estimated time:

Tags:

reactive work

Description

Observation¶

Bot does not ignore Development/Leap job groups and could block update approvals due to broken development tests.
See http://dashboard.qam.suse.de/blocked and look for "leap"

Problem¶

Likely regression due to https://github.com/openSUSE/qem-bot/commit/d4d33720d183ba30b63529577e2bbad700b238cd
or https://github.com/openSUSE/qem-bot/commit/c869a5cb7a56cdb5c3ba33f64e086f34c64ce5b9#diff-dbb33d499407c366ab760f232[…]e02dad0dd506c87b478b8007cf496ad

Suggestions¶

Look hard at the above commits and try it out with "--dry-run" and fix it. We at least know that jobs are still ignored, e.g. https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1044528#L2663 shows "INFO: Ignoring job '9078831' in development group 'Maintenance: Leap 15.4 Incidents'" so there is at least some ignoring going on

History
Notes
Property changes

Actions

Copy link

Updated by okurz almost 2 years ago

Assignee changed from osukup to okurz
Target version set to Ready

Actions

Copy link

Updated by okurz almost 2 years ago

Description updated (diff)

Actions

Copy link

Updated by livdywan almost 2 years ago

Subject changed from Bot do not ignore Development/Leap job groups to qem-bot does not ignore Development/Leap job groups as it should size:M
Description updated (diff)
Status changed from New to Workable

Actions

Copy link

Updated by okurz almost 2 years ago

Due date set to 2022-07-22
Status changed from Workable to In Progress

Following instructions in https://github.com/openSUSE/qem-dashboard/issues/61 I did:

smachinectl shell postgresql
sudo -u postgres psql dashboard_db
select count(*) from openqa_jobs where flavor ~ 'Leap' and version = '15.4' and group_id=432;

and got

 count 
-------
   228
(1 row)

I just deleted them with

delete from openqa_jobs where flavor ~ 'Leap' and version = '15.4' and group_id=432;

I could also just have created a temporary table and move there for investigation or just delete the not passed jobs but nevermind. Let's see if they reappear. I will monitor.

Actions

Copy link

Updated by okurz almost 2 years ago

Status changed from In Progress to Feedback

Jobs haven't reappeared since then. Likely still the same issue as https://github.com/openSUSE/qem-dashboard/issues/61 and #109310 due to an existing incident id being reused.

Actions

Copy link

Updated by okurz almost 2 years ago

there were some Leap 15.3 jobs which I refrained from deleting myself, but osukup helped with that today. I think we need to improve or at least provide such guidance in docs.

Actions

Copy link