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 over 2 years ago.
Updated 5 months ago.
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)
- 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
- 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
- Tags set to qe-yast-refinement
- Target version set to Current
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
- 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
- Assignee set to tinawang123
- Status changed from Workable to In Progress
- Status changed from In Progress to Workable
- Assignee deleted (
tinawang123)
Unassigning, still plenty of work in #113734 for assignee.
- Status changed from Workable to New
- Priority changed from Normal to Low
- Target version deleted (
Current)
- Status changed from New to Rejected
Improvements in logging were done by QE Core, old ticket.
Also available in: Atom
PDF