Project

General

Profile

Actions

action #119581

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

Track: how to distinguish these tags(bootloader, grub, inst-bootmenu) in needles

Added by jgwang over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
-
Start date:
2022-10-31
Due date:
% Done:

0%

Estimated time:

Description

Description

when reviewing the openQA job, I find that the needle "bootloader-ofw-12spX-grub2-20221027" has the tags "bootloader" and "grub2", but the process is different with different tag in "boot_local_disk"(bootloader_setup.pm) function, such as:

sub boot_local_disk {                                                                                                         
    if (get_var('OFW')) {                                                                                                     
        # TODO use bootindex to properly boot from disk when first in boot order is cd-rom                                    
        wait_screen_change { send_key 'ret' };                                                                                
        # Currently the bootloader would bounce back to inst-bootmenu screen after pressing 'ret'                             
        # on 'local' menu-item, we have to check it and send 'ret' again to make booting properly                                     
        if (check_screen(['bootloader', 'inst-bootmenu'], 30)) {                                                              
            record_info 'bounce back to inst-bootmenu, send ret again';                                                       
            send_key 'ret';                                                                                                   
        }                                                                                                                     
        my @tags = qw(inst-slof grub2);                                                                                       
        push @tags, 'encrypted-disk-password-prompt' if (get_var('ENCRYPT'));                                                 
        assert_screen(\@tags);
        if (match_has_tag 'grub2') {                                                                                          
            diag 'already in grub2, returning from boot_local_disk';                                                          
            stop_grub_timeout;                                                                                                
            return;                                                                                                           
        }

the code will send "ret" again if the matched needle has "bootloader" or "inst-bootmenu" tag, so the above openQA job failed.

go further, I find that openQA/we are difficult to distinguish the difference between these needles with "bootloader", "grub2" and "inst-bootmenu" tags, such as:

bootloader-ofw-12spX-grub2-20221027  ==> tags: "bootloader", "grub2"
bootloader-ofw-20150724              ==> tags: "bootloader", "inst-menu"
bootmenu-SLE_-textmode-20210706.json ==> tags: "bootloader", "grub2"
bootloader_uefi-20170718             ==> tags: "bootloader-grub2", "inst-bootmenu"

these needles has two tags, and the process is different with the tags in our code, so I think we need to make one needle with one tag, and make clear the definition of "bootloader", "inst-bootmenu", "grub2" and other key tags.

could you have any suggestion about this issue?


Related issues 1 (0 open1 closed)

Related to qe-yam - action #121654: Need ensure grub_test_snapshot to select read-only snapshot in grubRejected2022-12-07

Actions
Actions #1

Updated by geor over 1 year ago

  • Parent task set to #118336
Actions #3

Updated by JERiveraMoya over 1 year ago

  • Priority changed from Normal to Low

we wanted to make atomic the steps for bootloader a time ago, but we didn't find the moment and it is something that is not really our scope, but that would be very useful, in that sense with small test modules you can have that 1:1 with needles.
On the other hand we don't want to invest much on Power KVM as it is unsupported virtualization, which is the example that you described above.

@geor does it solve the issue your PR?

Actions #4

Updated by geor over 1 year ago

  • Status changed from New to Resolved

JERiveraMoya wrote:

we wanted to make atomic the steps for bootloader a time ago, but we didn't find the moment and it is something that is not really our scope, but that would be very useful, in that sense with small test modules you can have that 1:1 with needles.
On the other hand we don't want to invest much on Power KVM as it is unsupported virtualization, which is the example that you described above.

@geor does it solve the issue your PR?

Yes, the PR solves the issue. I m marking it as resolved

Actions #5

Updated by leli over 1 year ago

  • Related to action #121654: Need ensure grub_test_snapshot to select read-only snapshot in grub added
Actions #6

Updated by JERiveraMoya over 1 year ago

  • Parent task changed from #118336 to #121876
Actions

Also available in: Atom PDF