action #174508
opencoordination #169654: [epic] Create test scenarios for Agama
Retrieve logs when we fail sync with agama in booting
0%
Description
Motivation¶
For example when repos takes long time to be retrieved as we use at the end of this module needles to sync with the UI if if this part fails, we need some agama logs. We should consider also how to recover logs at this point in other architectures different than quemu
Example: https://openqa.suse.de/tests/16209465#step/boot_agama/14
Acceptance criteria¶
- AC1: Agama logs are also retrieved for the last step of the bootloader
- AC2: Answer to developers is provided about sporadic repo refresh problem.
Additional information¶
Slack conversation: https://suse.slack.com/archives/C02CLB2LB7Z/p1734414800010199?thread_ts=1734358459.072729&cid=C02CLB2LB7Z
Updated by JERiveraMoya about 23 hours ago
leli wrote in #note-1:
Maybe we can add a variable to note the phase such as the end of boot_agama, then post_failhook upload agama logs depend the value of the variable.
without magic variables, we could just run the function that retrieve the logs and ignore failures.
Updated by rainerkoenig about 21 hours ago
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
Updated by rainerkoenig about 16 hours ago
Updated by JERiveraMoya about 3 hours ago
- Description updated (diff)
btw we were asked by developers to provide logs when encounter this problem:
https://openqa.suse.de/tests/16197507#step/boot_agama/14
basically they want to know why the refresh of the repos is so slow, now I think I set it up to 4 minutes, but even though something got stuck:
https://suse.slack.com/archives/C02CLB2LB7Z/p1734414800010199?thread_ts=1734358459.072729&cid=C02CLB2LB7Z
Please, let's answer that question in this bug also running 20x runs with the unattended default installation.