Project

General

Profile

action #105085

coordination #105073: [Epic] Improve logging in openQA

[Research:24h] Identify which post_fail_hook is used by each module and document its action

Added by JRivrain 4 months ago. Updated 3 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Target version:
Start date:
2022-01-19
Due date:
% Done:

0%

Estimated time:

Description

Currently the logging in openQA is a often chaotic, sometimes redundant, sometimes some things are missing.

In order to make it more consistent, we need to identify what logs are collected by each module

Scope

y2_installbase.pm <- y2_base.pm <- opensusebasetest.pm

Acceptance criteria

AC1: Generate a list of modules, with which post_fail_hook it uses.
AC2: describe what logs are collected by each post_fail_hook.
AC3: List other modules different from y2_installbase that we use in our test (to work in follow-up ticket).

History

#1 Updated by JRivrain 4 months ago

  • Subject changed from Idenfy which post_fail_hook is used by each module in Yast group to Idenfy which post_fail_hook is used by each module in Yast group, and what it does

#2 Updated by JRivrain 4 months ago

  • Subject changed from Idenfy which post_fail_hook is used by each module in Yast group, and what it does to Identify which post_fail_hook is used by each module in Yast group, and what it does

#3 Updated by JRivrain 4 months ago

  • Tags set to qe-yast-refinement

#4 Updated by JERiveraMoya 4 months ago

  • Target version set to Current

#5 Updated by JERiveraMoya 3 months ago

To start we could limit the scope here to installation where we mainly use y2_installbase.pm as parent, therefore we could check post_fail_hooks methods in the following files:
y2_installbase.pm -> y2_base.pm -> opensusebasetest.pm

#6 Updated by JERiveraMoya 3 months ago

  • Tags deleted (qe-yast-refinement)
  • Tracker changed from coordination to action
  • Subject changed from Identify which post_fail_hook is used by each module in Yast group, and what it does to [Research:24h] Identify which post_fail_hook is used by each module and document its action
  • Description updated (diff)
  • Status changed from New to Workable

Also available in: Atom PDF