Project

General

Profile

Actions

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.

Status:
Rejected
Priority:
Low
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).


Related issues 1 (1 open0 closed)

Related to openQA Tests - coordination #68794: [qe-core][functional][epic] rework postfail hooksBlockedszarate2020-03-31

Actions
Actions #1

Updated by JRivrain over 2 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 #2

Updated by JRivrain over 2 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 #3

Updated by JRivrain over 2 years ago

  • Tags set to qe-yast-refinement
Actions #4

Updated by JERiveraMoya over 2 years ago

  • Target version set to Current
Actions #5

Updated by JERiveraMoya over 2 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 #6

Updated by JERiveraMoya over 2 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
Actions #7

Updated by tinawang123 almost 2 years ago

  • Assignee set to tinawang123
Actions #8

Updated by tinawang123 almost 2 years ago

  • Status changed from Workable to In Progress
Actions #9

Updated by szarate almost 2 years ago

Actions #10

Updated by JERiveraMoya almost 2 years ago

  • Status changed from In Progress to Workable
Actions #11

Updated by JERiveraMoya almost 2 years ago

  • Assignee deleted (tinawang123)

Unassigning, still plenty of work in #113734 for assignee.

Actions #12

Updated by JERiveraMoya over 1 year ago

  • Status changed from Workable to New
  • Priority changed from Normal to Low
  • Target version deleted (Current)
Actions #13

Updated by JERiveraMoya 5 months ago

  • Status changed from New to Rejected

Improvements in logging were done by QE Core, old ticket.

Actions

Also available in: Atom PDF