Project

General

Profile

Actions
Copy link

action #165833

closed

coordination #163919: [epic] Create automation setup for testing Agama

Ensure agama automation test get logs when issue happened

Added by leli 7 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
High
Assignee:
leli
Target version:
-
Start date:
2024-08-27
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-sep-sprint

Description

Motivation

Ensure agama automation test get logs when issue happened before installation finished. This should include support enough logs, and enable to upload logs when issue happened on all arches.
For modules 'boot_agama', 'auto', 'agama', should give logs when issue happened.
Regarding kernel params, maybe we are not passing some of them that helps with the logs, please be aware or that and compare with booting with bootloader_start.pm

Main motivation is that having logs sooner when something break can allow us to report to developers faster and get new builds with problem fix also a good pace.

Acceptance criteria

  • AC1: Ensure agama automation test get logs when issue happened.
Actions
Copy link
 #1

Updated by leli 7 months ago

  • Subject changed from Ensure agama automation test get logs when issue happened to Ensure agama automation test get logs when issue happened
  • Description updated (diff)
Actions
Copy link
 #2

Updated by leli 7 months ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by leli 7 months ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by leli 7 months ago

  • Assignee set to leli
Actions
Copy link
 #5

Updated by JERiveraMoya 7 months ago

  • Tags set to qe-yam-aug-sprint
  • Description updated (diff)
  • Status changed from New to In Progress
  • Parent task set to #163919
Actions
Copy link
 #6

Updated by leli 7 months ago

This test https://openqa.opensuse.org/tests/4436551#step/boot_agama/14 failed but can't upload logs for login failed. On investigation, the agama installer service failed to start which caused it can't recognize the live password, verified on manual test.

Actions
Copy link
 #7

Updated by leli 7 months ago ยท Edited

Set console=ttyS0 in bootloader parameter will fix the btrfs kernel message block login issue. https://openqa.opensuse.org/tests/4439399#step/auto/6

Set console=console=ttyS0 console=tty kernel.softlockup_panic=1 Y2DEBUG=1, it is ok also, https://openqa.opensuse.org/t4439418

Actions
Copy link
 #8

Updated by JERiveraMoya 7 months ago

  • Priority changed from Normal to High

sorry, I forgot to set proper priority, all agama tickets should be set to High priority unless there is some exception.

Actions
Copy link
 #9

Updated by JERiveraMoya 7 months ago

  • Tags changed from qe-yam-aug-sprint to qe-yam-sep-sprint
Actions
Copy link
 #11

Updated by leli 6 months ago

The module 'boot_agama' and 'auto' cover installation process and after installation, since after installation the system login password would be set as 'nots3cr3t' by default. So the easy way for us is to set the live password as 'nots3cr3t' to avoid password conflict before and after installation.

Actions
Copy link
 #12

Updated by leli 6 months ago

PR submitted to make logs to ignore kernel message. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20094

Actions
Copy link
 #13

Updated by leli 6 months ago

  • Status changed from In Progress to Resolved

Checked recent builds, logs are collected for modules of 'boot_agama', 'auto', 'agama' when issue happened.

Actions
Copy link

Also available in: Atom PDF