Project

General

Profile

action #105909

o3 logreports - Ignoring invalid group {"name":"123"} when creating new job

Added by tinita 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-02-03
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

We see the following warnings on o3:

# /var/log/openqa
[2022-02-01T10:13:49.572322Z] [warn] [pid:21258] Ignoring invalid group {"name":"38"} when creating new job 2170243
...
[2022-02-15T09:03:56.226220Z] [warn] [pid:11636] Ignoring invalid group {"id":"146"} when creating new job 2189548
[2022-02-15T09:09:29.985440Z] [warn] [pid:9896] Ignoring invalid group {"id":"146"} when creating new job 2189550

Just for the record, it is not the same as #106880.


Related issues

Related to openQA Infrastructure - action #105828: 4-7 logreport emails a day cause alert fatigue size:MResolved2022-02-032022-02-17

History

#1 Updated by okurz 5 months ago

  • Project changed from openQA Infrastructure to openQA Project

These are all things that could be better handled by the software itself, not infrastructure issues

#2 Updated by okurz 5 months ago

  • Parent task deleted (#105828)

All of these issues can be fixed but the alert ticket is addressed by preventing the alert so better not treat as subtask

#3 Updated by okurz 5 months ago

  • Related to action #105828: 4-7 logreport emails a day cause alert fatigue size:M added

#4 Updated by tinita 5 months ago

  • Description updated (diff)

#5 Updated by tinita 4 months ago

  • Related to action #106880: Job template name ... is already used in job group error logged on o3 size:M added

#6 Updated by mkittler 4 months ago

  • Description updated (diff)

#7 Updated by tinita 4 months ago

  • Related to deleted (action #106880: Job template name ... is already used in job group error logged on o3 size:M)

#8 Updated by okurz about 1 month ago

  • Category set to Feature requests
  • Status changed from New to Feedback
  • Assignee set to okurz
  • Target version changed from future to Ready

#9 Updated by okurz about 1 month ago

  • Due date set to 2022-06-03

PR was merged.

That actually caused a regression which I fixed in https://github.com/os-autoinst/openQA/pull/4666

To rollback the installation on o3 I did

zypper -n in --oldpackage /var/cache/zypp/packages/devel_openQA/noarch/openQA*-4.6.1653043420.03e4026-lp153.5004.1.noarch.rpm

and in combination for the fallout of testing https://github.com/os-autoinst/os-autoinst/pull/1696 I did

result="result='failed'" failed_since="2022-05-20 17:00" ./openqa-advanced-retrigger-jobs
worker=openqaworker7 failed_since="2022-05-20 17:00" ./openqa-advanced-retrigger-jobs

https://github.com/os-autoinst/openqa-logwarn/pull/38 for the removal from monitoring ignoring.

#10 Updated by okurz about 1 month ago

  • Due date deleted (2022-06-03)
  • Status changed from Feedback to Resolved

https://github.com/os-autoinst/openqa-logwarn/pull/38 merged so problem solved and monitoring has the rule removed again to keep it clean.

Also available in: Atom PDF