Project

General

Profile

Actions

action #169273

closed

[SLEM] Repair SelfInstall scenario for SLEM6.1 for aarch64

Added by ph03nix 3 months ago. Updated 5 days ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2024-11-04
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Since the SLEM 6.1 GMC build, the aarch64 images do not have the console= parameter set by default in such a way, that allows the Graphical terminal to work. This causes test failures in
firstrun.

We fixed this issue in other test runs by adding the EXTRABOOTPARAMS=console=tty setting, see e.g. https://openqa.suse.de/tests/15818020#. This adds the additional console=tty setting in the bootloader_uefi step of the test run. For The SelfInstall ISOs there is no way of adding extra boot parameters yet. We need to find a way to add the console=tty setting to the boot parameters there.

Acceptance criteria

  • AC1: The aarch64 test runs for SelfInstall isos work

Further references


Related issues 1 (0 open1 closed)

Related to Containers and images - action #169243: [SLE-Micro] Repair JeOS-firstboot wizard for SLEM ppc64le imagesResolvedmloviska2024-11-04

Actions
Actions #1

Updated by ph03nix 3 months ago

  • Related to action #169243: [SLE-Micro] Repair JeOS-firstboot wizard for SLEM ppc64le images added
Actions #2

Updated by ph03nix 3 months ago

  • Subject changed from [slem] Repair SelfInstall scenario for SLEM6.1 to [slem] Repair SelfInstall scenario for SLEM6.1 for aarch64
Actions #3

Updated by ph03nix 3 months ago

  • Priority changed from Normal to High
Actions #4

Updated by slo-gin about 2 months ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #5

Updated by slo-gin 15 days ago

  • Priority changed from High to Normal

This ticket was set to High priority but was not updated within the SLO period. The ticket will be set to the next lower priority Normal.

Actions #6

Updated by ph03nix 13 days ago

  • Project changed from openQA Tests (public) to Containers and images
  • Subject changed from [slem] Repair SelfInstall scenario for SLEM6.1 for aarch64 to [SLEM] Repair SelfInstall scenario for SLEM6.1 for aarch64
  • Category deleted (Bugs in existing tests)
  • Priority changed from Normal to High
Actions #7

Updated by ph03nix 13 days ago

  • Tags changed from slem to slem, to-be-refined
  • Status changed from Workable to Blocked

Needs refinement

Actions #8

Updated by mloviska 11 days ago

This has been fixed in slem 6.2 by adding rd.kiwi.install.pass.bootparam=console=tty. Do we need to do the same for slem 6.1?

Actions #9

Updated by ph03nix 10 days ago

  • Tags changed from slem, to-be-refined to slem
  • Status changed from Blocked to Workable

mloviska wrote in #note-8:

This has been fixed in slem 6.2 by adding rd.kiwi.install.pass.bootparam=console=tty. Do we need to do the same for slem 6.1?

I would guess so, yes.

Actions #10

Updated by mloviska 6 days ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska
Actions #15

Updated by mloviska 5 days ago

  • Status changed from In Progress to Resolved

There is certain instability with grub2 handler in ppc, and a few of container engine user-space issues as quadlet failures.
The main goal of the ticket was reached, aarch64 selfinstall works, however I have taken the opportunity to fix other issues that were related to job group settings as well.

Actions

Also available in: Atom PDF