action #105085: [Research:24h] Identify which post_fail_hook is used by each module and document its action - qe-yam - openSUSE Project Management Tool

Actions

Copy link

action #105085

closed

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 almost 3 years ago. Updated about 1 year ago.

Status:

Rejected

Priority:

Low

Assignee:

Target version:

Start date:

2022-01-19

Due date:

% Done:

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).

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by JRivrain almost 3 years 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

Actions

Copy link

Updated by JRivrain almost 3 years 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

Actions

Copy link

Updated by JRivrain almost 3 years ago

Tags set to qe-yast-refinement

Actions

Copy link

Updated by JERiveraMoya almost 3 years ago

Target version set to Current

Actions

Copy link

Updated by JERiveraMoya almost 3 years 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

Actions

Copy link

Updated by JERiveraMoya almost 3 years 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