action #105085
Updated by JERiveraMoya 4 months ago
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 Proposal: write a simple script to generate a list of each module, which post_fail_hooks it uses, and maybe what logs are collected. Or do it manually if it seems more simple.
#### Acceptance criteria
**AC1**: AC1: Generate a list of modules, with which post_fail_hook it uses.
**AC2**: 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).
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 Proposal: write a simple script to generate a list of each module, which post_fail_hooks it uses, and maybe what logs are collected. Or do it manually if it seems more simple.
#### Acceptance criteria
**AC1**: AC1: Generate a list of modules, with which post_fail_hook it uses.
**AC2**: 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).