QA (public) » openQA Project (public) » openQA Infrastructure (public)

Note that smelt is empty/ broken, so this is why the dashboard shows no incidents - the data is actually still there and accessible via deep links

Confirmed in the database that it is indeed related to the SMELT problem. The bot synced an empty list to the dashboard and there are no active incidents:

dashboard_db=# select * from incidents where active = true;
 id | number | rr_number | project | approved | emu | active | packages | review | review_qam
----+--------+-----------+---------+----------+-----+--------+----------+--------+------------
(0 rows)

And just for the record, this is the pipeline job which did the sync: https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1212601

Maybe we can also improve a bit and abort such attempt? We probably did an empty post, instead we can preserve the old state as a better behavior.

jbaier_cz wrote:

And just for the record, this is the pipeline job which did the sync: https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1212601

Maybe we can also improve a bit and abort such attempt? We probably did an empty post, instead we can preserve the old state as a better behavior.

In that case it would be best to show that the data is outdated, though, e.g. Data hasn't been updated since... to avoid hiding the fact that new data is not coming in anymore.

cdywan wrote:

In that case it would be best to show that the data is outdated, though, e.g. Data hasn't been updated since... to avoid hiding the fact that new data is not coming in anymore.

There is already "Last updated ago" message on the top which should be enough to indicate that.

jbaier_cz wrote:

There is already "Last updated ago" message on the top which should be enough to indicate that.

That message on the dashboard also includes RabbitMQ updates for job results. So it is not directly correlated to updates from the bot.