Project

General

Profile

Actions

action #66114

closed

[functional][u] Use bootloader_start instead of arch/backend specific test module

Added by SLindoMansilla over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Refactor/Code Improvements
Target version:
SUSE QA - Milestone 30
Start date:
2020-04-27
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Motivation

At the moment there are different arch/backend specific bootloader modules

  • bootloader
  • bootloader_hyperv
  • bootloader_s390
  • bootloader_svirt
  • bootloader_uefi
  • bootloader_zkvm

They cause to repeat the following conditional schedule:

conditional_schedule:
    bootloader:
        ARCH:
            'aarch64':
                - boot/uefi_bootmenu
            's390x':
                - installation/bootloader_zkvm
        MACHINE:
            'svirt-xen-pv':
                - installation/bootloader_svirt
            'svirt-xen-hvm':
                - installation/bootloader_svirt

There is a module that should implement all those arch/backend specific behavior:

  • bootloader_start

Acceptance criteria

  • AC: bootloader_start is the only test module scheduled for handling bootloader in functional job group

Tasks

  1. Adapt bootloader_start to work in all scenarios (arch, backend, etc) from QSF-U job group.
  2. Replace the conditional schedule with bootloader_start.

Related issues 1 (0 open1 closed)

Has duplicate openQA Tests - action #40625: [sle][functional][u][hyperv] test fails in bootloader_hyperv - key stroke issueRejectedSLindoMansilla2018-09-05

Actions
Actions #1

Updated by SLindoMansilla over 4 years ago

  • Description updated (diff)
  • Assignee deleted (SLindoMansilla)
Actions #2

Updated by SLindoMansilla over 4 years ago

  • Category set to Refactor/Code Improvements
  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions #3

Updated by zluo over 4 years ago

I checked bootloader_start.pm only question is about xen pv regarding the bsc#961638. So this is not clear to me atm.

Actions #4

Updated by SLindoMansilla over 4 years ago

zluo wrote:

I checked bootloader_start.pm only question is about xen pv regarding the bsc#961638. So this is not clear to me atm.

I haven't looked at the code but, the bug is mentioning that the boot menu is not shown via VNC, which I would consider expected since there is no display manager started at that point. The boot menu needs to be handled via serial console. Am I missing something?

See https://openqa.suse.de/tests/4285725

Actions #5

Updated by dheidler over 4 years ago

  • Assignee set to dheidler
Actions #6

Updated by dheidler over 4 years ago

  • Status changed from Workable to In Progress
Actions #8

Updated by SLindoMansilla over 4 years ago

  • Has duplicate action #40625: [sle][functional][u][hyperv] test fails in bootloader_hyperv - key stroke issue added
Actions #9

Updated by dheidler over 4 years ago

  • Status changed from In Progress to Feedback
Actions

Also available in: Atom PDF