Project

General

Profile

Actions

action #97481

closed

qam dashboard including development job group

Added by dzedro over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2021-08-25
Due date:
2021-09-08
% Done:

0%

Estimated time:

Description

Allegedly it's because JeOS: Development group was moved from non-devel to devel group. [1]
I guess it's blocking approx. half of updates on http://dashboard.qam.suse.de/blocked

[1] https://chat.suse.de/channel/qac/thread/MqX5SfykQzpNokELR?jump=J2iRPTz9nZqvrRYsv

Actions #1

Updated by okurz over 2 years ago

  • Due date set to 2021-09-08
  • Status changed from New to Feedback
  • Assignee set to okurz
  • Target version set to Ready

I'm sorry, I don't understand. Could you please add more details? I assume you see a problem but I don't know what the problem is. What is the expected result?

Actions #2

Updated by dzedro over 2 years ago

  • Assignee deleted (okurz)
  • Target version deleted (Ready)

okurz wrote:

I'm sorry, I don't understand. Could you please add more details? I assume you see a problem but I don't know what the problem is. What is the expected result?

When you open dashboard http://dashboard.qam.suse.de/blocked and search for JeOS: Development, this group should be not there.

Actions #3

Updated by dzedro over 2 years ago

  • Assignee set to okurz
  • Target version set to Ready
Actions #4

Updated by okurz over 2 years ago

  • Status changed from Feedback to New
  • Assignee deleted (okurz)
  • Priority changed from High to Urgent

@osukup is this a regression due to the ill-communicated move of incident test approval from openQABot to bot-ng? If yes, please revert that ASAP

Actions #5

Updated by livdywan over 2 years ago

I don't see any relevant-looking changes in bot-ng or openQABot 🤔️ We really need to figure out where these things are changed, and where we can review such changes easily and quickly.

Actions #6

Updated by osukup over 2 years ago

https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/9

  • for current state it needs touch qem dashboard database
Actions #7

Updated by osukup over 2 years ago

  • Status changed from New to Feedback
  • Assignee set to osukup

dashboard_db=# DELETE FROM openqa_jobs WHERE job_group='JeOS: Development';
DELETE 180
dashboard_db=#

Actions #8

Updated by osukup over 2 years ago

  • Status changed from Feedback to In Progress

this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?

Actions #9

Updated by kraih over 2 years ago

osukup wrote:

this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?

There is no data added to the database from RabbitMQ. There is just one query that updates the state of jobs, that't it.

UPDATE openqa_jobs SET status = ?, updated = NOW() WHERE job_id = ? RETURNING job_id;
Actions #10

Updated by osukup over 2 years ago

kraih wrote:

osukup wrote:

this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?

There is no data added to the database from RabbitMQ. There is just one query that updates the state of jobs, that't it.

UPDATE openqa_jobs SET status = ?, updated = NOW() WHERE job_id = ? RETURNING job_id;

oh ... thx for info,

Actions #11

Updated by osukup over 2 years ago

conditions for ignoring jobs simplified and database manually cleaned ..

Actions #12

Updated by osukup over 2 years ago

  • Status changed from In Progress to Feedback
Actions #13

Updated by osukup over 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF